JP2014179068A - Application support system, application file creation support server, and application file creation support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an application file creation support system for supporting the creation of an application file from a technological information file such as a thesis.SOLUTION: Necessary information such as the name of an inventor and the like and a technological information file are caused to transmit from a PC of a research worker (inventor) via a site for accepting the technological information file such as a thesis (S301), and a HTML application file is automatically generated based on the technological information file in a server having received the necessary information and the technological information file, and after being stored in a predetermined folder, this HTML application file is notified to an administrator (S302 to S304). The administrator side performs an application procedure by an electronic application soft using the stored HTML file of the predetermined folder.

Description

  The present invention relates to an application support system for easily creating a patent application document from a technical information file such as a paper.

  Research institutions such as universities publish their research results through society and papers as a traditional method of social return, and at the same time, use the method of social return through patent applications. In particular, after the incorporation of a university, further promotion of industry-academia collaboration is required, and patents are used as the tool.

  When comparing a paper with a patent application document (specification), there are some differences in its character, but it is common in that it is a technical document for the purpose of publishing the technology. It is considered that it is sufficiently possible to divert and utilize patent application documents (however, it is generally difficult to obtain a patent with an appropriate scope of rights simply by diverting the description of a paper. is expected). In relation to this, Patent Document 1 discloses a conventional technique related to automatically generating a patent application document from a paper.

JP 2002-207720

  As mentioned above, there are universities that are actively applying for patents, but there are still a considerable number of researchers at such institutions who prioritize publication of papers over patent applications. Existing. Since many people apply for on-campus processing such as notification of invention after writing a paper first, if the grace period until publication of the paper is short, the preparation of patent application documents will not be in time and the application will be made after publication It has also happened. In this way, when it becomes an application after publication, it will not be possible to obtain a patent for a country that does not have provisions regarding exceptions to loss of novelty (or limited reasons for application). Even if this is the case, it cannot be globally licensed and its value will be significantly reduced. It can be said that this is a loss of the organization and a loss of the country's external industrial competitiveness.

  The only complete measure to solve this problem is to file a patent application before it becomes publicly known, and ideally, thorough enlightenment to researchers to achieve this, It is difficult to always ask for the cooperation of a series of work of “Creating an Invention Notification to Application Procedure” with the understanding of a very busy researcher (currently, slowly moving in that direction) It ’s hard to make a big improvement quickly). Therefore, as a next best measure, an emergency evacuation application (at least covering the contents to be published) to avoid becoming publicly known at the expense of completeness as a patent application document. However, in this case, what is important is that this can be done quickly with the simplest possible procedure. The above-mentioned problem has arisen due to the fact that it takes time to create patent application documents, so the most important point in emergency evacuation applications is that they can be processed extremely easily and quickly. (In particular, it needs to be something that does not require much effort for the researcher (inventor)).

  A system that automatically generates patent application documents based on technical information documents such as papers is considered effective in order to make an emergency evacuation application easily and quickly. The technique disclosed in Patent Document 1 can meet such a purpose. However, the technique disclosed in Patent Document 1 discriminates a predetermined item in a paper or the like and creates a patent application document by diverting the description to the corresponding application document item (for example, “Academic” Based on the description on the “consideration” or “introduction” of the paper, the “claims” column and the “means for solving the problem” column of the patent specification are created. It could only be handled by technical documents (articles) in the format. In addition, a certain amount of work is required when preparing documents. ("If you click" Embodiment of the invention "", etc., there is a risk that it will be difficult to use without some knowledge of the format of the application documents.)

  SUMMARY OF THE INVENTION In view of the above-described points, an object of the present invention is to provide a system that supports the creation of an application file that can be used in a simple procedure for an inventor who has a technical information file such as a paper. In addition, for the purpose of providing an application file creation support system, etc., that allows managers such as the Intellectual Property Department to smoothly use application software, etc., for applications that can handle a wide variety of technical information files The object is to provide a file creation support system. It is another object of the present invention to provide a system for providing a proxy service for emergency evacuation applications to universities and the like. (Not all these objectives must be achieved, and if any objective can be achieved, it can be useful.)

  An application support system according to the present invention is an application support system configured by an application file creation support server, an administrator terminal device, an inventor terminal device, and a network, the application file creation support server Is connected to the administrator terminal device and the inventor terminal device via the network so that the application file creation support server can communicate the technical information file and the invention from the inventor terminal device via the network. A technical information file acquisition unit for acquiring information on the applicant, an application generation unit for automatically generating an application using the acquired inventor information and preset applicant information, and the acquired technical information file for each page. Automatically generate a statement by converting each image file to the automatically generated paragraph number Using the automatic booklet generation unit and the generated application and specification, a predetermined format application file in a format accepted by the electronic application software is automatically generated, and the predetermined format application is stored in a storage area accessible by the administrator terminal device. And an application file generation unit for storing the file.

  According to the above configuration, the inventor simply uploads a technical information file (for example, electronic data of a paper) using the inventor's terminal device, and the system automatically generates a file for filing and stores it in a predetermined area. This is stored. In addition, a person in charge of application processing (for example, an employee of the Intellectual Property Department) only has to apply for a file automatically stored in a predetermined area using electronic application software. Therefore, it becomes possible to file an application with a simple procedure for both the inventor and the application clerk. Further, according to the above configuration, the technical information file is converted into an image file for each page, and the description is automatically generated by pasting each image file on each automatically generated paragraph number. Since a specification automatic generation process can be executed with a uniform process for a file of a simple format, the versatility is high.

  A first application file creation support server according to the present invention is an application file creation support server that supports creation of application documents for patent applications or utility model registration applications, and a control unit that controls the entire apparatus , A storage unit, a communication unit, a file imaging unit, and a technology for acquiring the technical information file and the inventor information via the network by the communication unit and storing them in the storage unit or the external storage device in association with each other An information file acquisition unit; an application generation unit that automatically generates an application using the inventor information; and the technical information file is converted into an image file by the file imaging unit, and each image file is pasted to a paragraph number. A specification automatic generation unit that automatically generates a specification by attaching, and a predetermined format output format that the electronic application software accepts using the generated application and specification. An application file generation unit that automatically generates a file, and the predetermined format application file is stored in a preset storage area of the storage unit or the predetermined format application file is stored in a preset storage area of an external device And a file storage processing unit for sending information from the communication unit.

  According to the second application file creation support server of the present invention, in the first application file creation support server, the file imaging unit performs printing using a print function of application software corresponding to the technical information file. Output data is acquired, and conversion from the print output data into the image file is executed.

  According to the above configuration, application software associated with each file format (for example, Microsoft Word (registered trademark) for a file with an extension of doc) is started, and printing is performed using the printing function of the software. Output data is acquired, and conversion processing to an image file is executed based on the output data. Normally, any application software has a printing function, and the format of output data is standardized for compatibility with a printer (or printer driver). Therefore, by using this, even if technical information files (electronic files such as papers) are in various formats, it is possible to execute the automatic specification generation process with uniform processing. High and convenient for users.

  The third application file creation support server according to the present invention provides a site for accepting transmission of the technical information file and the inventor information from the file owner in the first or second application file creation support server. By providing a technical information file reception site presenting section to be presented, the technical information file and the inventor information are acquired through the site.

  According to the above configuration, the inventor's work can only be performed by accessing the technical information file reception site, inputting necessary information, and uploading the technical information file.

  According to a fourth application file creation support server of the present invention, in any one of the first to third application file creation support servers, in the technical information file and inventor information acquisition process by the technical information file acquisition unit Obtained application date information or date of publication of the technical information file is also obtained, and in the storage process by the file storage processing unit, the date and time derived directly or indirectly from the application filing date information or publication date information The application file includes a daily folder storage processing unit that stores the predetermined format application file in a daily folder corresponding to the above, or the scheduled application date information or the publication in the storage process of the predetermined format application file in the storage area Preliminary filing date information or previous A file transfer processing unit on the day for moving the predetermined format application file to a predetermined folder when there is the predetermined format application file whose date and time derived directly or indirectly from the scheduled release date information corresponds to the current day; Features.

  According to the above configuration, the predetermined format application file is stored in each folder corresponding to the scheduled application date, or the predetermined format application file having the scheduled application date is stored in a predetermined folder (for example, “today application scheduled folder”). It will be moved and stored. “Date and time derived directly or indirectly from scheduled application date information or scheduled release date information” means the scheduled application date (or scheduled application date and time). , Refers to the date (or date and time) obtained directly from the information, and if the date of release date information is obtained, the date (or date and time) derived from the date of release according to a predetermined condition (for example, the date of release date) 1 day before the application date). As a result, when the application clerk is stored in each folder corresponding to the scheduled application date, the application clerk selects the folder corresponding to the current day and processes the application based on the files in the folder. The application process of the matter according to can be executed. On the other hand, when the corresponding file on the current day is moved to a predetermined folder, the application processing of the matter corresponding to the deadline can be executed by always applying the application processing based on the files in the same folder (predetermined folder).

  The fifth application file creation support server according to the present invention is the fourth application file creation support server, which includes a reference number including information indicating that the application is automatically generated by the application file creation support server. An automatic reference number generation unit for automatically generating information; and a date / time function unit, and an application is automatically generated using the reference number in the application generation process by the application generation unit, and is obtained by the date / time function unit The date is derived directly or indirectly from the scheduled filing date information or planned publication date information when the date reaches or has passed directly or indirectly derived from the planned filing date information or planned publication date information. The application number of the electronic application software is acquired based on the reference number information. If there is no accepted file corresponding to the reference number by searching the folder where the accepted file obtained is stored, or search the list output file output from the electronic application software and corresponding to the reference number When there is no scheduled application date information or application number information to be applied, a received file confirmation unit is provided that transmits warning information to the administrator based on administrator information set in advance.

  According to the above configuration, a serial number is automatically generated and assigned to each case, and based on the serial number, the presence or absence of an accepted file obtained by the application processing of the electronic application software or output from the electronic application software is output. The system automatically searches for whether or not there is information indicating that the application has been filed in the list output file (project list). If it is determined that there is no information, warning information is transmitted to the administrator. As a result, the system automatically checks whether or not the application processing for each case has been performed on the scheduled application date. If there is no information that can be determined that the application processing has been performed, an administrator (for example, an application clerk) Since a warning is issued, it is possible to suppress omissions in procedures.

  According to the sixth application file creation support server of the present invention, in any one of the first to fifth application file creation support servers, it is determined whether the inventor is an employee based on the inventor information. An employee discriminating unit for discriminating and an administrator site presenting unit for presenting an administrator site for accepting information from the manager are included, whereby the employee discriminating unit judges that an inventor who is not an employee is included. In the case where it is determined, the information on the corresponding technical information file and the inventor information are displayed on the administrator site, and when the approval information is input from the administrator, the predetermined format application file is automatically generated. The execution of the process is permitted.

  According to the above configuration, when an inventor who is not an employee (a person who is not in an employment relationship) is included, the input of the administrator's approval information is required for automatic processing in the system. Administrators (e.g., application clerk) are not able to take over reservations for the interests of persons who are not in an employment relationship (rights to receive patents), and therefore cannot be applied independently by an institution with this system. It is confirmed that the approval has been obtained through the confirmation with the partner organization, etc., and the automatic generation process of the application file is executed. As a result, the occurrence of an approved application can be suppressed.

  According to the seventh application file creation support server of the present invention, in the fourth or fifth application file creation support server, a date / time function unit, a date obtained by the date / time function unit, and the scheduled filing date information or publication Compare the date and time derived directly or indirectly from the scheduled date information, determine whether this is shorter than the preset period, and if it is shorter, allow the automatic generation processing of the predetermined format application file And a grace period determining unit.

  According to the above configuration, when the period until the scheduled application date is longer than a predetermined period (for example, one month), the automatic generation process of the predetermined format application file is not executed. In cases where this system is only used as an application to urgently evacuate publications such as papers, for example, if there is a grace period of one month or longer, the system will not The automatic generation processing by the present system is not executed as the application processing (judgment of whether to apply or manual creation of application documents) should be performed.

  According to an eighth application file creation support server of the present invention, in any one of the first to seventh application file creation support servers, the technical information file is colored by the technical information file reception site presenting unit. If the technical information file is indispensable in color, it is generated as a foreign language document in the automatic generation of the application and replaced with the automatic generation processing of the specification. If the technical information file is not a PDF file, it is converted into a PDF file, and a process of pasting it on the item name of “foreign language document” is executed.

  According to the above configuration, when the technical information file is indispensable in color, the application file is automatically generated as a foreign language document. In the case where a technical information file (electronic file such as a paper) is created in color, there is a possibility that important information may be lost if it is made grayscale. Japanese patent electronic applications do not allow color images to be attached as of 2012, and mechanical gray scales in accordance with this may result in the loss of important information as described above. May not be able to satisfy the original purpose of “preventing public announcement by publicly publishing etc.”. In this regard, since it is possible to attach a color PDF file in a foreign language document application, the lack of information is suppressed by applying as a foreign language document.

  According to a ninth application file creation support server of the present invention, in any of the third to eighth application file creation support servers, the technical information file reception site presenting unit provides technical field information related to the technical information file. In addition, the technical field information and the keyword information are acquired via the site by presenting the site for inputting the keyword information, and the technical information file is associated with the technical field information and the keyword information in advance in the storage unit or in advance. It is stored in the storage area of the set external device.

  According to the above configuration, technical field information and keyword information related to the technical information file are stored in association with each other. As a result, the database of technical information files such as the inventor's papers in his / her institution can be made simultaneously.

  According to a tenth application file creation support server of the present invention, in any of the fourth to ninth application file creation support servers, a date and time function unit, a date obtained by the date and time function unit, an application date, A period elapse confirmation unit that determines whether or not this period has exceeded a preset period and, if exceeded, transmits predetermined period elapse information to the manager based on the preset manager information And an application withdrawal document generation unit that automatically generates an application withdrawal document for an application for which the predetermined period has elapsed.

  According to the above-described configuration, the notification regarding withdrawal and the automatic generation processing of the application withdrawal document are performed for the case for which the predetermined period has elapsed. This system has a strong urgent evasive meaning that only mechanically copies papers, etc., and has an aspect premised on a later priority claim application. (It is not a denial of the case of suspending the application due to response, etc.), but the application was filed in an emergency evacuation manner, but in the end there are many cases where the procedure for obtaining the right to the invention is not continued. Since it is not a good idea from the viewpoint of cost and the like, it is necessary to notify the administrator.

  An eleventh application file creation support server according to the present invention is an application file creation support server that supports creation of application documents for a patent application or utility model registration application, and a control unit that controls the entire apparatus A storage unit in which customer login information and applicant information are stored in association with each other, a communication unit, a file imaging unit, a login processing unit for performing a login process, and a technology through a network by the communication unit An application using a technical information file acquisition unit that acquires an information file and inventor information and associates the information file and the inventor information and stores them in the storage unit or the external storage device, and the applicant information specified by the inventor information and login An application generation unit that automatically generates a file, and the technical information file is converted into an image file for each page by the file imaging unit. A specification automatic generation unit that automatically generates a specification by pasting a file to each automatically generated paragraph number, and a predetermined format application file in a format accepted by the electronic application software using the generated application and specification An application file generation unit for automatically generating the application file.

  According to the above configuration, the automatic generation service of the predetermined format application file based on the technical information file is provided by the system that enables the automatic generation processing of the specification to be executed with uniform processing for various types of files. Can be provided for each customer.

  A twelfth application file creation support server according to the present invention is an eleventh application file creation support server, in which agent login information is stored in the storage unit, and there is login from the agent. The technical information file, the predetermined format application file, or an application file obtained from the electronic software, and a request for input of a technical information file etc. corresponding to the technical proposal file. A claim plan acquisition unit that acquires the claim plan information obtained by the above and a claim plan presentation unit that presents the claim plan to a customer who has transmitted the technical information or the like.

  According to the above configuration, the technical information file etc. obtained from the customer is presented to the agent side, the input of the complaint proposal according to the contents of the technical information file etc. is accepted, and the obtained complaint proposal is received by the customer (technical The processing presented to the information file sender) is performed by the system. Thereby, the customer who receives the provision of this service can confirm the draft of the claim created by the agent based on the contents of the technical information file.

  A thirteenth application file creation support server according to the present invention is a twelfth application file creation support server, which provides input of evaluation information for a complaint plan when the complaint proposal is presented to the customer. And the evaluation information obtained thereby is stored in the storage unit or the external storage device in association with the ID of the agent who input the claim plan, in response to a request from the customer or a request from the agent, An agent evaluation information acquisition / presentation section for presenting the evaluation information is provided.

  According to the above configuration, the evaluation information is stored in association with the agent for the draft proposal created by the agent based on the contents of the technical information file, and the request from the customer or the request from the agent Accordingly, since the evaluation information is presented, it is possible to provide a service that presents information that evaluates the ability to create a claim after looking at an actual claim plan.

  A fourteenth application file creation support server according to the present invention is the thirteenth application file creation support server, wherein the agent evaluation information acquisition / presentation section requests an application from the agent. The customer is requested to input evaluation information regarding the agent who is the application request destination, and the evaluation information obtained thereby is stored in the storage unit or the external storage device in association with the ID of the agent. In response to a request from or a request from an agent, a process for presenting the evaluation information is further performed.

  According to the above configuration, it is possible to obtain evaluation information based on the actual request result for the agent who is the request destination from the customer who made the application request, and provide a service for presenting the evaluation information Can do.

  The fifteenth application file creation support server according to the present invention is any one of the twelfth to fourteenth application file creation support servers, and when the claim proposal is presented to the customer, the claim An application request reception / notification processing unit that presents an application request input means to the agent who has input the proposal, and presents an application request to the agent when there is an input to the agent, and the application request A billing processing unit that performs billing processing for the agent when the information is provided.

  According to the above configuration, when a request for work is generated for the agent based on the provision service of the draft proposal created by the agent, the charging process for the agent is performed. It is possible to provide a service that is charged only when an actual job is requested.

  A first agent evaluation / introduction service support server according to the present invention includes a control unit that controls the entire apparatus, a storage unit that stores requester login information and agent login information, a communication unit, and a login unit. A request processing information is acquired from a log-in processing unit that performs processing and a requester who has logged in via the network by the communication unit, and this is associated with the requester information specified by the log-in in the storage unit or the external A request information acquisition unit to be stored in the storage device, a request information presentation unit for presenting the request information to the agent when the agent logs in, and input of corresponding information to the agent And a correspondence information acquisition unit for acquiring the correspondence information obtained by this request and a correspondence information presentation unit for presenting the correspondence information to the customer who transmitted the request information. And wherein the Rukoto.

  According to the above configuration, the request information obtained from the requester is presented to the agent side, and the response information according to the content of the request information (advice for the request content, suggestion of a solution, suggestion of response policy, etc.) The system performs a process of accepting the input and presenting the obtained correspondence information to the requester. Thereby, the client who receives the provision of the service can confirm the correspondence information created by the agent based on the contents of the request information.

  The second agent evaluation / introduction service support server according to the present invention is a first agent evaluation / introduction service support server, wherein the storage unit stores the agent ID information and the corresponding conditions for the agent. Corresponding condition information acquisition unit that stores information or / and inoperable information in association with each other, and acquires from the requester corresponding condition information or / and incompatible information corresponding to the inoperable information via the network When the request information is presented to the agent, the corresponding condition information acquired from the client is compared with the corresponding condition information or / and the unacceptable information, so that a suitable agent can be obtained. The request information is presented to the user.

  Agency services are generally highly specialized, and therefore there is usually a certain range of fields that each can serve as a specialty. In addition, there may be cases where the customer falls under a relationship with an existing client and cannot newly receive a proxy. In such a situation, according to the above configuration, the agent ID and corresponding condition information (for example, various information such as own specialized field information, business type, delivery date, amount, etc. can be considered) or / and incapable Information (similarly, field information, industry type, delivery date, amount of money, specific company name that cannot be supported, etc. can be considered) are stored in association with each other, and corresponding condition information (same field information, , Delivery date, amount of money, specific company name, etc. can be considered), and based on these, the requested information is presented to the appropriate agent, so an efficient service is provided be able to. In addition, since the request information is unnecessarily presented, it is excellent from the viewpoint of confidentiality.

  The third agent evaluation / introduction service support server according to the present invention is the first or second agent evaluation / introduction service support server, and is a proxy for presenting request information in the acquisition of the request information. An agent designation information acquisition unit for accepting designation is provided, and the request information is presented to the designated agent when the request information is presented to the agent.

  According to the above configuration, the requester can designate the agent (s) who wants to present the request information.

  The fourth agent evaluation / introduction service support server according to the present invention is any one of the first to third agent evaluation / introduction service support servers, and when the corresponding information is presented to the customer The evaluation information for the corresponding information is requested to be input, and the evaluation information obtained thereby is stored in the storage unit or the external storage device in association with the ID of the agent who has input the corresponding information. In accordance with a request or a request from an agent, an agent evaluation information acquisition / presentation unit that presents the evaluation information is provided.

  According to the above configuration, the evaluation information for the correspondence information created by the agent based on the content of the request information is stored in association with the agent, in response to a request from the client or a request from the agent, Since the evaluation information is presented, it is possible to provide a service that presents information that evaluates the ability after viewing the actual correspondence information (that is, the quality of service provided by the agent).

  A fifth agent evaluation / introduction service support server according to the present invention is a fourth agent evaluation / introduction service support server, in which the requester ID information, the attribute information of the requester, and the like are stored in the storage unit. Are stored in association with each other, and in storing the evaluation information, the ID information or the attribute information of the client who has input the evaluation information is stored in association with the evaluation information.

  According to the fourth agent evaluation / introduction service support server, the agent's service is evaluated by the client, and this is presented, but the evaluation depends on the attributes of the client (for example, differences in job type). The tendency of the way may change. The side using the evaluation information may be more helpful if the information can be viewed in consideration of such points. On the other hand, according to the fifth agent evaluation / introduction service support server, the evaluation information and the attribute information of the requester are stored in association with each other. Therefore, when the evaluation information is presented, the requester (= evaluator) ) Can be displayed according to the attribute information.

  The sixth agent evaluation / introduction service support server according to the present invention is the fourth or fifth agent evaluation / introduction service support server, and in the presentation of the evaluation information, the evaluation information reaches a predetermined number. Alternatively, the acquired evaluation information is not targeted for presentation until a predetermined period has elapsed.

  If the evaluation information is immediately reflected (presented), the evaluated agent may immediately know if someone has entered the evaluation information (if there is only one person using this system, Naturally, you can see that the person evaluated.) A client who inputs evaluation information may want to avoid having the agent know that he / she has made a bad evaluation. On the other hand, according to the above configuration, since the evaluation information is not subject to presentation until the predetermined number of evaluation information or a predetermined period elapses, someone has input the evaluation information to the evaluated agent. Immediate deterrence is prevented.

  A seventh agent evaluation / introduction service support server according to the present invention is a sixth agent evaluation / introduction service support server, wherein the client is set with the predetermined number or the predetermined period. .

  According to the above configuration, the evaluator can set the predetermined number or the predetermined period in “Evaluation information is not to be presented until the evaluation information reaches a predetermined number or until a predetermined period elapses”. That is, for example, if the predetermined number is set to 100, the evaluation information made by the user after 100 evaluation information is accumulated becomes the subject of presentation, and if set to 0, the subject becomes the subject of presentation immediately (controls the timing of release of the evaluation information made by the user). Can be).

  An eighth agent evaluation / introduction service support server according to the present invention is any one of the fourth to seventh agent evaluation / introduction service support servers, wherein the storage unit includes requester ID information, The attribute information registered by the requester is stored in association with each other, and when the evaluation information is input, the requester ID that inputs the evaluation information and the identification according to the number of registrations of the attribute information The service information is stored in association with each other.

  According to the above configuration, it becomes possible to associate more specific service information (for example, points, cashback information, etc.) with a client who has entered evaluation information after registering more attribute information. . In other words, in order to increase the value of this system, it is indispensable to enrich the evaluation information (= improve the value as a DB), so we offer a service that gives more preferential treatment to clients who have enriched the information. By providing, it gives incentives to actions that lead to DB value enhancement.

  A ninth agent evaluation / introduction service support server according to the present invention is any one of the first to eighth agent evaluation / introduction service support servers, wherein the corresponding information is presented to the customer. A request input / notification processing unit that presents a request input means for the agent who has input the correspondence information, and presents a request to the agent when there is a request input for the agent, and A billing processing unit that performs billing processing for the agent when the request is presented.

  According to the above configuration, when a request for work is generated for the agent based on the use of this system, the billing process for the agent is performed, so there was an actual request for work. It is possible to provide a service that is charged only in such a case.

  A tenth agent evaluation / introduction service support server according to the present invention is a ninth agent evaluation / introduction service support server, wherein the request information and / or the agent ID corresponding to the request is provided. Alternatively, when request information is presented to the agent, a request condition information is stored in association with the requester information, and a request condition information is acquired from the requester via the network. The correspondence condition information acquired from the requester and the performance information are compared, and the request information is not presented to an unsuitable agent.

  As mentioned above, agency services are highly specialized and have limited fields of responsibility, and may not be accepted due to conflicts or other reasons. On the other hand, according to the above configuration, corresponding condition information (a variety of information such as field information, industry type, delivery date, amount of money, specific company name, etc. can be considered) is obtained at the time of request, and this and the performance information in this system On the basis of this, the request information is presented to the appropriate agent based on this, so that an efficient service can be provided. In addition, since the request information is unnecessarily presented, it is excellent from the viewpoint of confidentiality.

  A first agent evaluation / introduction service support program according to the present invention provides an information processing apparatus including a control unit that controls the entire apparatus, a calculation unit, a storage unit, and a communication unit. A step of performing a login process in response to a login request, a step of acquiring request information via the network by the communication unit, and storing the request information in association with the requester information in the storage unit or the external storage device; Requesting the agent to input the request information when there is a login from a person, and requesting the agent to input corresponding information, and acquiring the corresponding information and storing it in association with the agent information And a step of presenting the correspondence information to the customer who has transmitted the correspondence information.

  The second agent evaluation / introduction service support program according to the present invention is a first agent evaluation / introduction service support program, in which the agent ID information and the corresponding conditions for the agent are stored in the storage unit. Information or / and unacceptable information are stored in association with each other, and acquiring the condition information corresponding to the condition information or / and unacceptable information from the requester via the network; In the process of presenting request information to a person, the request condition is presented to a suitable agent by comparing the corresponding condition information acquired from the requester with the corresponding condition information or / and the incapable information. And a step of executing.

  The third agent evaluation / introduction service support program according to the present invention is the first or second agent evaluation / introduction service support program, and receives the designation of the agent in the acquisition of the request information; In the process of presenting request information to the agent, the step of presenting request information to the designated agent is executed.

  A fourth agent evaluation / introduction service support program according to the present invention is any one of the first to third agent evaluation / introduction service support programs, wherein the correspondence information is presented to the customer. A step for requesting input of evaluation information for the correspondence information, a step for storing the evaluation information obtained thereby in association with the ID of the agent who inputted the correspondence information, a request from the customer or the agent And a step of presenting the evaluation information in response to a request from.

  A fifth agent evaluation / introduction service support program according to the present invention is a fourth agent evaluation / introduction service support program, which includes requester ID information, attribute information of the requester, and the like in the storage unit. Are stored in association with each other, and in the storage of the evaluation information, a step of storing the ID information or the attribute information of the client who has input the evaluation information in association with the evaluation information is executed.

  The sixth agent evaluation / introduction service support program according to the present invention is the fourth or fifth agent evaluation / introduction service support program, and in the presentation of the evaluation information, the evaluation information reaches a predetermined number. Or until the predetermined period passes, the step which does not make said acquired evaluation information a presentation object is performed.

  A seventh agent evaluation / introduction service support program according to the present invention is a sixth agent evaluation / introduction service support program, and executes a step of causing a client to set the predetermined number or the predetermined period. It is characterized by.

  An eighth agent evaluation / introduction service support program according to the present invention is any one of the fourth to seventh agent evaluation / introduction service support programs, wherein the storage unit includes requester ID information, The attribute information registered by the requester is stored in association with each other, and when the evaluation information is input, the requester ID that inputs the evaluation information and the identification according to the number of registrations of the attribute information The step of associating and storing service information is executed.

  A ninth agent evaluation / introduction service support program according to the present invention is any one of the first to eighth agent evaluation / introduction service support programs, wherein the correspondence information is presented to the customer. A step of presenting a request input means for the agent who has input the correspondence information, a step of presenting a request to the agent when there is a request input for the agent, and presentation of the request And performing a billing process for the agent after performing the above.

  A tenth agent evaluation / introduction service support program according to the present invention is a ninth agent evaluation / introduction service support program, which includes the request information and / or the agent ID corresponding to the request. Or the step of storing the requester information in association with the result information, the step of acquiring the corresponding condition information from the requester via the network, and the requester when presenting the request information to the agent Comparing the acquired correspondence condition information with the result information, a step of not presenting the request information to an unsuitable agent is executed.

  According to the file creation support server for application according to the present invention, it becomes possible to file an application with a simple procedure for both the inventor and the application clerk. In addition, the technical information file is converted into an image file for each page, and the specification is automatically generated by pasting each image file on each automatically generated paragraph number. In addition, the automatic generation process of the specification can be executed by a uniform process, so that the versatility is high.

  In addition, according to the agent evaluation / introduction service support server according to the present invention, as a system for matching an agent and a client, request information obtained from the client can be handled by a plurality of agents. We can provide advice on request contents, suggestions of solutions, suggestions of response policies, etc.). Usually, when using a highly specialized agency service, it is difficult to select the most preferable agent by comparing the corresponding capabilities. However, according to the present invention, this is possible. In addition, since the evaluation information for the actual response capability (response information) can be accumulated, a service for selecting an agent who requests a job with reference to the evaluation information is provided. Can do.

1 is a block diagram illustrating an outline of an application support system according to a first embodiment. FIG. 1 is a block diagram showing an outline of a file creation support server for application according to a first embodiment. The flowchart which shows the outline of the whole operation | movement of the application assistance system which concerns on Embodiment 1. FIG. The flowchart which shows the outline of the whole operation | movement of the file creation support server for an application which concerns on Embodiment 1. FIG. Flowchart showing processing operation of the researcher PC according to the first embodiment (operation when applying for an emergency paper application) The flowchart which shows the processing operation of the file preparation support server for an application at the time of accepting the application for the paper emergency application concerning Embodiment 1 The flowchart which shows the processing operation at the time of receiving the application for the paper emergency application in the system which concerns on Embodiment 1 when the file preparation support server for an application registers information in DB. The flowchart which shows the whole processing operation which produces | generates automatically the HTML file for an application in the system which concerns on Embodiment 1. FIG. The flowchart which shows the process which automatically produces | generates the application part in the HTML file automatic generation preservation | save process for an application in the system which concerns on Embodiment 1. The flowchart which shows the process which images a file, such as a paper, for every page in the system which concerns on Embodiment 1 in the HTML file automatic generation preservation | save process for an application The flowchart which shows the process which produces | generates the specification part automatically in the system which concerns on Embodiment 1 in the HTML file automatic generation preservation | save process for an application. The flowchart which shows the process which automatically produces | generates the HTML file for application as a foreign document application in the system which concerns on Embodiment 1. 10 is a flowchart showing immediate process file movement / notification processing in the system according to the first embodiment; The flowchart which shows the file movement / notification process on the day in the system which concerns on Embodiment 1 A flowchart showing withdrawal confirmation / notification processing in the system according to the first embodiment. The flowchart which shows the operation | movement of the procedure completion confirmation process in the system which concerns on Embodiment 1. FIG. The flowchart which shows the operation | movement of the application application on the day in the system which concerns on Embodiment 1, and the procedure completion confirmation process The flowchart which shows the operation | movement of the immediate application matter in the system which concerns on Embodiment 1, and procedure completion confirmation processing The flowchart which shows the operation | movement of the withdrawal application case in the system which concerns on Embodiment 1, and procedure completion confirmation processing The flowchart which shows the whole process which the administrator uses this system in the system which concerns on Embodiment 1. FIG. The flowchart which shows the operation | movement of the process which produces | generates the top screen for administrators in the system which concerns on Embodiment 1. FIG. The flowchart which shows operation | movement of the administrator approval process in the system which concerns on Embodiment 1. FIG. The flowchart which shows the processed matter registration process performed in the system which concerns on Embodiment 1 at the time of an administrator approval process In the system which concerns on Embodiment 1, the flowchart which shows the process which produces | generates the application part automatically in the HTML file automatic generation preservation | save process for an application performed at the time of an administrator approval process The figure which shows an example of a structure of the application matter table which concerns on Embodiment 1. The figure which shows an example of a structure of (a) staff table, (b) job code table, and (c) job code table according to the first embodiment, respectively. The figure which respectively shows an example of a structure of (a) temporary user registration table, (b) language code table, (c) field code table, (d) employment code table according to the first embodiment. The figure which shows an example of a structure of the administrator setting information table which concerns on Embodiment 1. FIG. The figure which shows an example of a structure of the application file management table which concerns on Embodiment 1. The figure which shows an example of a structure of the display screen of the page for application application which concerns on Embodiment 1. FIG. The figure which shows an example of a structure of the input item confirmation page which concerns on Embodiment 1. The figure which shows an example of a structure of each warning page which concerns on Embodiment 1. The figure which shows an example of a structure of the administrator top screen which concerns on Embodiment 1. FIG. The figure which shows an example of a structure of the application information input screen which concerns on Embodiment 1. The figure which shows an example of a structure of the withdrawal information input screen which concerns on Embodiment 1. The figure which shows an example of a structure of the approval process screen which concerns on Embodiment 1. The figure which shows an example of a structure of the approval process separate screen which concerns on Embodiment 1. The figure which shows an example of a structure of the administrator setting screen which concerns on Embodiment 1. The figure which shows the specification HTML template file which concerns on Embodiment 1. FIG. The figure which shows an example of the HTML file for an application produced | generated by the system which concerns on Embodiment 1 The figure which shows the foreign language document HTML template file which concerns on Embodiment 1. The figure which shows an example of the foreign language document HTML file for an application produced | generated by the system which concerns on Embodiment 1 (A) The figure which shows an application withdrawal document HTML template file which concerns on Embodiment 1, (b) The figure which shows an example of the application withdrawal document HTML file for the procedure produced | generated by the system The figure which shows the foreign language document HTML template file (model file of the specification part used by the process of FIG. 46) which concerns on Embodiment 1. FIG. The figure which shows an example of the foreign language document HTML file (file automatically generated by the process of FIG. 46) produced | generated by the system which concerns on Embodiment 1. FIG. In the system which concerns on Embodiment 1, the flowchart which shows another process which automatically produces | generates the HTML file for application as a foreign document application A block diagram showing an outline of an application support system according to a second embodiment The flowchart which shows the outline of the whole operation | movement of the file creation support server for an application which concerns on Embodiment 2. FIG. The flowchart which shows operation | movement of the customer corresponding site process in the system which concerns on Embodiment 2. FIG. The flowchart which shows the processing operation which receives the request of the urgent paper application concerning Embodiment 2 In the system which concerns on Embodiment 2, the flowchart which shows the whole processing operation which produces | generates automatically the HTML file for an application. The flowchart which shows operation | movement of the individual item detailed information registration process in the system which concerns on Embodiment 2. FIG. The flowchart which shows the processing operation | movement of the unfiled matter information correction process which concerns on Embodiment 2. FIG. The flowchart which shows the processing operation of the claim proposal display process which concerns on Embodiment 2. FIG. The flowchart which shows the operation | movement of the office corresponding site process in the system which concerns on Embodiment 2. FIG. The flowchart which shows operation | movement of the case application processing on the day in the system which concerns on Embodiment 2. The flowchart which shows operation | movement of the withdrawal process in the system which concerns on Embodiment 2. FIG. 10 is a flowchart showing an operation of procedure end notification processing in the system according to the second embodiment. The figure which each shows an example of a structure of (a) customer table, (b) office table, (c) patent attorney table concerning Embodiment 2 The figure which shows an example of a structure of the application matter table which concerns on Embodiment 2. FIG. The figure which shows an example of a structure of the application file management table which concerns on Embodiment 2. FIG. The figure which shows an example of a structure of (a) charge table and (b) procedure table which concern on Embodiment 2, respectively. The figure which shows an example of a structure of the evaluation table which concerns on Embodiment 2. The figure which shows an example of a structure of the complaint plan table which concerns on Embodiment 2. The figure which shows an example of a structure of the top screen of the customer site which concerns on Embodiment 2. FIG. The figure which shows an example of a structure of the display screen of the page for application application which concerns on Embodiment 2. FIG. The figure which shows an example of a structure of the input item confirmation page which concerns on Embodiment 2. FIG. The figure which shows an example of a structure of the information correction page of the application matter which applied according to Embodiment 2. The figure which shows an example of a structure of the information correction page of the unfiled matter which concerns on Embodiment 2. The figure which shows an example of a structure of the claim proposal display page which concerns on Embodiment 2. The figure which shows an example of a structure of the claim evaluation page which concerns on Embodiment 2. The figure which shows an example of a structure of the evaluation page which concerns on Embodiment 2. The figure which shows an example of a structure of the top screen of the site for patent attorneys concerning Embodiment 2. The figure which shows an example of a structure of the complaint proposal input screen which concerns on Embodiment 2. The figure which shows an example of a structure of the claim proposal correction confirmation screen which concerns on Embodiment 2. The figure which shows an example of a structure of the personal evaluation screen which concerns on Embodiment 2. The figure which shows an example of a structure of the registration information display change screen which concerns on Embodiment 2. FIG. The block diagram which shows the outline of the agent matching support system which concerns on Embodiment 3. FIG. The flowchart which shows the outline of the whole operation | movement of the agent matching support server which concerns on Embodiment 3. FIG. 10 is a flowchart showing the operation of requester correspondence site processing in the system according to the third embodiment. The flowchart which shows operation | movement of the process which performs request reception which concerns on Embodiment 3. 10 is a flowchart showing the processing operation of comment display processing according to the third embodiment. The flowchart which shows the operation | movement of the agent corresponding site process in the system which concerns on Embodiment 3. FIG. The figure which shows an example of a structure of (a) requester table and (b) agent table which concern on Embodiment 3, respectively. The figure which shows an example of a structure of the request matter table which concerns on Embodiment 3. FIG. The figure which shows an example of a structure of the evaluation table which concerns on Embodiment 3. The figure which shows an example of a structure of the request correspondence plan table which concerns on Embodiment 3. The figure which shows an example of a structure of the top screen of the site for clients concerning Embodiment 3. The figure which shows an example of a structure of the display screen of the page for request input which concerns on Embodiment 3. The figure which shows an example of a structure of the display screen of the page for agent selection which concerns on Embodiment 3. The figure which shows an example of a structure of the comment display page which concerns on Embodiment 3. The figure which shows an example of a structure of the top screen of the site for agents concerning Embodiment 3.

  Hereinafter, embodiments of the present invention will be specifically described with reference to the drawings. In addition, the following embodiment is one form at the time of actualizing this invention, Comprising: This invention is not limited within the range.

(Embodiment 1)
The application support system according to the present embodiment, for example, in a research institution such as a university, uploads a technical information file such as a paper to a predetermined site by a researcher, so that an HTML file for patent application from the paper (technical information file) A (predetermined format application file) is automatically generated and stored in a predetermined folder. For the researcher (inventor), the work is simply to upload the paper to the specified site. Also, the person in charge of the intellectual property department etc. applies the HTML file for application saved in the specified folder with the application software. Therefore, simple and quick processing is possible for both the inventor and the person in charge of intellectual property. As a result, even though the period until publication of a paper is very limited, an application based on a paper (emergency evacuation application; hereinafter referred to as “paper emergency application” for the sake of convenience) before the invention becomes known. Even in countries where there is no provision such as grace period or limited, it is possible to obtain the right by claiming priority under the Paris Convention based on the emergency application of the paper. It is obtained.

  FIG. 1 is a block diagram illustrating an outline of an application support system according to the first embodiment. As shown in the figure, a head office system 11, a department system 12, the Internet 13, and a patent office system 14 are main components. The head office system 11 and the department system 12 are university systems. The headquarter system 11 is a network system provided in the headquarters, and the department system 12 is provided for each graduate school, for example, and is connected to each other via a campus network via routers (115, 122) provided therein.

  In the headquarters system 11, an application file creation support server 111, an application HTMLDB 112 (external storage device), an administrator PC 113 (administrator terminal device), and an application file DB 114 (external storage device) are provided on the internal network side. ) And a router 115 or the like. Also, an internal server such as various business servers is provided in the internal network, and a public server such as a Web server is provided in the DMZ segment. The administrator PC 113 in this embodiment is a PC of a person in charge who performs application work, and has electronic application software installed. The administrator PC 113 is connected to the Internet 13 via a firewall 116 and a router (or gateway) 117 (appropriately connected to the Internet via an Internet service provider or the like). Internet applications can be filed.

  The department system 12 is a network system provided for each graduate school, for example, and each researcher's PC 121 (inventor terminal device) can send and receive information to and from the application file creation support server 111 via the internal network. Is possible. As will be described later, the “document emergency application application site” provided by the application file creation support server 111 is accessed using a browser installed on the PC 121, and necessary information such as inventor information By simply sending a technical information file such as a paper, the researcher's procedure for urgent application of the paper is completed.

  FIG. 2 is a block diagram showing an outline of the application file creation support server 111. The application file creation support server 111 includes a main body 1111, a keyboard and mouse 1113 as input devices, a monitor 1114 as an output device, a storage device 1112 (storage unit) such as an HDD, and the like. The main body 1111 includes a CPU 11111, a memory 11112, an input / output control unit 11114, a communication unit 11113 that transmits and receives information to and from the network, and the like. The application file creation support server 111 can transmit / receive information to / from the internal network via the communication unit 11113, thereby transmitting / receiving information to / from the administrator PC 113, the researcher PC 121, and the like. The storage device 1112 stores an administrator setting information table 11122 (FIG. 28), an application file management table 11123 (FIG. 29), an application case table 11121 (FIG. 25), and the like. As will be described in detail later, the application file creation support server 111 presents a page such as “thesis emergency application site” via the campus network, collects necessary information from researchers and managers, and applies for the application file. The information necessary for generating each page of the site, an HTML template file to be described later, and the like are also stored in the storage device 1112. The application file creation support server 111 executes each process described in detail below, and a program for that is stored in the storage device 1112, and is a control unit and a calculation unit while reading the program into the memory 11112 as needed. The CPU 11111 performs various arithmetic processes and the like, and each process is executed by storing the result in the storage device 1112 or outputting it to another device. That is, according to each hardware resource such as a CPU and each program, each function processing unit (technical information file acquisition unit, application generation unit, specification automatic generation unit, application file generation unit, file imaging unit, file storage processing unit, Technical information file reception site presentation unit, file transfer processing unit on the day, automatic number generation unit, accepted file confirmation unit, employee discrimination unit, administrator site presentation unit, grace period discrimination unit, period progress confirmation unit, application withdrawal A document generation unit).

<Overview of overall system processing>
First, an overview of the overall processing of the application support system of the present embodiment will be outlined. FIG. 3 is a flowchart showing an outline of the overall operation of the application support system of this embodiment. The researcher (inventor) uses the researcher PC 121 to access the site for emergency application for dissertation provided as an on-campus site by the application file creation support server 111, and a technical information file such as a dissertation and necessary information ( The application file creation support server 111 that has received the information and the like is stored in the storage device 1112, the application file DB 114, or the like (S301). Next, the application file creation support server 111 executes a process of automatically generating an application HTML file using the information received in S301 (S302), and executes a process of saving it in a predetermined folder (S302). S303). If there is an urgent paper application, the administrator is notified of this (S304). An administrator (for example, an application clerk in the intellectual property department) uses application software (electronic application software distributed by the Patent Office) installed on the administrator PC 113 to “predetermined folder” by the process of S303. A process of converting the stored HTML file into a transmission file format of the application software and a process of transmitting (ie, filing) this are performed (S305). In this way, the researcher only sends a technical information file such as a paper and necessary information (S301), and the administrator also applies for an application document (HTML file) automatically generated by the system and stored in a predetermined folder. Since only the application is made by software (S305), it becomes possible to file an application with procedures as simple as possible for both the inventor and the manager (application staff).

<Overview of application file creation support server overall processing>
Next, an overview of the entire processing operation in the application file creation support server 111 will be described, and then each functional process constituting the entire process will be sequentially described in detail. FIG. 4 is a flowchart showing an outline of the overall operation of the application file creation support server 111, and the outline of the processing operation of the application file creation support server 111 will be described based on this flowchart.

  S401 to S404 form a loop for waiting for the occurrence of an event, and processing corresponding to the event is executed according to the occurrence of each event.

  When there is a request from the researcher PC 121 to access a site for an emergency application for a thesis (S401), the process proceeds to S405, and the acceptance process (technical information file such as an article and necessary information) by the site for the emergency application for an article A process of receiving information from the researcher PC and storing it in a predetermined folder is executed. The receiving process will be described in detail later. In the receiving process, it is determined whether or not the case is a case that can be accepted by the system. If the case is a case that can be accepted, a reception number is obtained as a return value. In S406 following the reception process (S405), it is determined whether or not there is this return value (reception number). If there is no return value (that is, if this system cannot accept it), the event generation wait loop in S401 to S404 is performed. Return to (No urgent application will be made using this system for the case). Also, in the acceptance process of S405, when information relating to the inventor is acquired and a person who has no employment relation is included in the inventor, 1 is set as the “approval flag” as management information, If it is not included, it is set to 0 and stored in the application matter table 11121 (FIG. 25) (in this embodiment, it is also set to 1 when the applicant is a person who has no employment relationship). In S407 following S406 after the reception process, it is determined whether or not the approval flag is 0. If it is not 0 (if it is 1), a process of notifying this to the administrator is executed ( S407 No → S410). As will be described in detail later, the administrator who receives the notification logs in to the system with administrator authority and approves the application for the case, and if it is approved, the system automatically generates an HTML file. Will be executed. The process related to the approval flag is a request for approval by the administrator before automatic processing in the system when the inventor is not a follower (a person who is not in an employment relationship). The ownership (right to receive a patent) of a person who is not in an employment relationship cannot be taken over by reservation, and therefore the institution that has this system cannot apply alone without permission. After confirming that approval has been obtained, the application file automatic generation process is executed. (In this embodiment, the administrator also needs to check if the applicant is a person who has no employment relationship.) ) Note that information necessary for automatically sending an email to the administrator, such as the email address of the administrator, is set in the storage device 1112 in advance. In this embodiment, the inventor (and the applicant) is assumed to be an employee, and when the application file is automatically generated, the application file is automatically generated. Regardless, the application file may be automatically generated after approval from the administrator.

  On the other hand, if the approval flag is 0 as a result of the determination process in S407 after the reception process, a process of automatically generating an application HTML file based on the data acquired in the reception process is executed (S408). Next, the process proceeds to S409, and when the scheduled application date is before today or the “immediate flag” is 1 (based on information obtained at the time of acceptance processing (S405) such as scheduled release date and flag immediately). As will be described in detail later, an immediate process file transfer / notification process is executed (S411). This process (S411) stores an HTML file related to the case in a folder for immediate processing, especially for a rushed case, and notifies the administrator. Upon receiving the notification, the administrator immediately performs a process of applying the application document (HTML file) stored in the immediate processing folder using the application software. In this way, it is possible to quickly process an application for a rushed case.

  When the processes of S405 to S411 are completed, the process returns to the loop process of S401 to S404 and waits for the next event to occur.

  In the loop processing of S401 to S404, when the time has reached midnight, processing for deleting files in the immediate processing folder, the current day processing folder, and the withdrawal folder is executed (S402 Yes). → S412). As will be clarified in the detailed explanation of each processing later, each folder stores files to be processed on that day, and when the date changes, the contents are cleared once and processed on that day. Only the files that should be stored are stored. In the present embodiment, processing is performed at midnight, but processing may be performed at the set time by setting an arbitrary time according to the operation of each engine. Although not particularly shown in FIG. 2, the file creation support server 111 for application includes a date / time function unit that provides a clock function, and the date / time function unit provides date / time information and a timekeeping function. Yes (for the clock function, the date / time function unit may be configured by acquiring the time from a time server on the network).

  In the loop processing of S401 to S404, when the time becomes “current day file transfer time”, the current day file transfer / notification processing is executed (S403 → S414). This processing is to copy the file to the processing folder for the day of the case where the scheduled filing date has arrived among the HTML files for application automatically generated and stored in S408. In the present embodiment, an HTML file for application is automatically generated in the process of S408 for the case accepted in S405 and stored in the HTMLL112 for application. From the cases stored in the DB 112, in the process of S414, The case to be processed is moved to the folder for current day processing (the storage area of the administrator PC 113), and the current day processing folder is cleared when the date changes after the application processing by the administrator ends (S412). When the current day file movement time is reached, the file of the matter to be processed on the current day is moved to the current day processing folder, and so on. As a result, the administrator only has to apply for a file that is always in the same folder (the folder for the day's processing), and the procedure becomes simple (it also prevents procedure errors). The “current file transfer time” is information set by the administrator and stored in the administrator setting information table 11122 (FIG. 28).

  In S415 subsequent to S414, it is determined whether or not the withdrawal management flag is 1. If it is 1, the process proceeds to S416 to execute withdrawal confirmation / notification processing. This process is a process for automatically generating an application withdrawal document for a “paper emergency application” made by the present system after a predetermined period of time and prompting the withdrawal of the application. One of the purposes of this system is to enable applications in each country by submitting “emergency papers” before the invention becomes publicly known through papers, etc. There are aspects that presuppose the subsequent application. Therefore, in an organization that considers that it is not necessary to continue the “emergency application” itself as an application, use the withdrawal management function to submit an “emergency application” at an appropriate time (for example, one year and three months after filing) ), It is possible to save unnecessary time and cost after that. The withdrawal management flag (whether or not the withdrawal management function is used) is information set by the administrator and stored in the administrator setting information table 11122 (FIG. 28), and is 0 when withdrawal management is unnecessary. Therefore, the process of S416 is not executed (No in S415 → S416 skip). In the present embodiment, the withdrawal confirmation / notification process (S416) is performed at the “current day file move time” (that is, the process at the same timing as the current day file move / notification process (S414)). The file transfer / notification process (S414) on the day may be set to be performed at a different time.

  In the loop processing of S401 to S404, when the time becomes “check time”, procedure end confirmation processing is executed (S403 → S413). This process is a process for confirming whether or not a procedure to be processed (such as an application procedure for an emergency paper application) has been executed. In the system of this embodiment, the application process is a process separate from the system process (process by the application software installed in the administrator PC 113), and information indicating that the procedure has been completed directly in the system is obtained. Therefore, the file output from the application software is checked from this system to check whether or not the procedure has been executed. “Check time” is information set by the administrator and stored in the administrator setting information table 11122 (FIG. 28). In the present embodiment, the check time is only one, but a plurality of check times may be set. For example, the procedure completion confirmation process may be executed when the folder clear process of S412 is performed.

  If there is an access request to the administrator site in the loop process of S401 to S404, the administrator operation process is executed (S404 Yes → S417). This processing is to make various settings related to the system, confirmation of each item, information input, and the like on an administrator site that can be operated with administrator authority (details will be described later).

  The above is the outline of the entire processing operation in the application file creation support server 111. Hereinafter, each functional process constituting the overall process will be sequentially described in detail.

<< Reception process by the site for the application for urgent paper application: details of the process of S405 in FIG. 4 >>
FIG. 5 shows the work of a researcher (inventor) using a researcher PC 121 to access a site for urgent application application and send a technical information file such as a paper and necessary information (inventor's information, etc.) Is a flowchart showing the processing operation of the researcher PC 121 at the time (although in the present embodiment, the web page of the researcher PC 121 is used to access the site for emergency paper application and input information, This does not mean that a program for performing the processing of FIG. FIG. 6 is a flowchart showing the processing operation of the application file creation support server 111 corresponding to the access request from the researcher PC 121, and corresponds to the processing of S405 in FIG. The paper emergency application acceptance process will be described below with reference mainly to FIGS.

  The researcher (inventor) uses the researcher PC 121 to access the site for the application for urgent paper application (URL is notified to the researcher in the university in advance, and this is accessed). As a result, the researcher PC 121 issues a request for sending a paper emergency application application page to the application file creation support server 111 (FIG. 5: S501). Upon receipt of this, the application file creation support server 111 executes the acceptance process of FIG. 6 (FIG. 4: S401 Yes → S405).

  In this embodiment, the use of this system is limited to access from within the university. Therefore, in S601 (FIG. 6), an access request to the urgent application application site is sent from within the university network. Whether or not there is an access from the campus is determined based on the IP address of the request source. If the access is not from within the university, a page notifying that only access from the university is available is transmitted and the process is terminated (FIG. 6). : S601 No-> S618). The researcher PC 121 that received this displays the unusable page and ends the application process (FIG. 5: S502 → S516). On the other hand, if the access is from within the campus network, the application file creation support server 111 transmits a paper emergency application application page (FIG. 6: S601 Yes → S602), and the researcher PC 121 that has received the page receives the request. A page is displayed (FIG. 5: S502 → S503). In this example, the access is limited to access from on-campus, but the access may be unlimited or may be restricted under other conditions.

  FIG. 30 shows a display screen example of the paper emergency application application page. In the present embodiment, the input information at the time of application is shown in FIG. Among them, applicant information (name, affiliation title, employment relationship, contact information), inventor information (name, affiliation title, contribution to invention, employment relationship, contact information), scheduled publication date (for example, publication of paper) Date, etc.), materials scheduled to be published (for example, Word files of papers), information on whether or not color is essential (if the material is created in color, if it is made black and white, the information is missing (the contents are unclear) The color of the document is required in the case where the data is required), and the language of the document is an essential input item. If there are a large number of inventors, clicking the “Add field” button adds an entry field for the inventor. Technical fields (technical fields of the invention) and keywords (keywords related to the invention) are arbitrary input items in this embodiment. In addition, information on “immediate application (a case that requires as soon as possible application processing)” is also an input item.

  The applicant (researcher) selects the “confirm input contents” button after completing the input items on the application application page of FIG. The input information is transmitted to the application file creation support server 111 by this selection (FIG. 5: S504 Yes → S505). Upon receipt of this, the application file creation support server 111 (FIG. 6: S603 Yes → S604) determines whether or not the essential input information has been input. A warning page as shown is transmitted (FIG. 6: S604 No → S613). The researcher PC 121 that has received the warning page displays this (FIG. 5: S506 → S512), and when the “OK” button is selected on the warning page, transmits it to the application file creation support server 111. (FIG. 5: S513 → S514), the process returns to S502. Upon receiving the OK information, the application file creation support server 111 (FIG. 6: S614 Yes) returns to S602 and transmits the paper emergency application application page to the researcher PC 121. At the time of the transmission, transmission is performed with the contents already input. On the side of the researcher PC 121 that has received this, necessary information is input again.

  If the required input items are satisfied in the determination processing in the application file creation support server 111, an input item confirmation page is transmitted to the researcher PC 121 (FIG. 6: S604 Yes → S605). FIG. 31 shows an example of the confirmation page display. This is displayed on the researcher PC 121 that has received the page (FIG. 5: S506 → S507). The researcher confirms the information, and if correction is necessary, selects the “return to input screen” button. If “return to input screen” is selected, the information is transmitted to the file creation support server 111 for application (FIG. 5: S508 → S515), and the process returns to S502. Upon receiving the “Return to input screen” instruction, the file creation support server 111 for application (FIG. 6: S606) returns to S602 and transmits the paper emergency application application page to the researcher PC 121 (at the time of transmission, input first. Send with completed content). On the side of the researcher PC 121 that has received this, necessary information is input again. On the other hand, if there is no problem in the content on the confirmation page in FIG. 31, the researcher selects the “Send input content” button. When the researcher PC 121 selects “send input contents”, it transmits this to the application file creation support server 111 (FIG. 5: S508 → S509), and receives the information, the application file creation support server In 111, the process proceeds to the DB registration process (FIG. 6: S606 → S607).

<<< DB Registration Process: Details of Process in S607 of FIG. 6 >>>
In S607 of FIG. 6, the information obtained by the application from the researcher, that is, the information obtained by inputting to the application application page of FIG. 30 is registered in the DB in association with the file (technical information file such as a paper). Perform the process. FIG. 7 is a flowchart showing the processing of S607 in FIG.

  In S701, a reception number is automatically generated, and a new record having the reception number as a primary key is generated in the application case table 11121 (FIG. 25) of the storage device 1112 of the application file creation support server 111. The receipt number is automatically assigned in accordance with a predetermined rule. In this embodiment, the symbol “E” indicating that the application is an emergency paper and the date of receipt (January 1, 2013) In this case, the receipt number is automatically generated by adding a hyphen after 130101) and assigning the serial number of the year (the number of cases accepted). The application item table 11121 (FIG. 25) is a table for storing information obtained by an application from a researcher and files such as papers in association with each other.

  In subsequent S702, the approval requirement flag of the corresponding record (the record corresponding to the reception number generated in S701) is set to 0 (the approval requirement flag is initialized).

The loop processing (S703 to S707) following S702 confirms whether the applicant and the inventor (there are a plurality of cases) have employment relations and whether or not there is data in the staff table. It is a process of registering. In S703, a process for searching whether there is data in the staff table (FIG. 26 (a)) from the name information of the application information is performed. If there is data, the corresponding ID (the process target is the inventor). If it is, the ID and the contribution degree) are registered in the corresponding record of the application item table 11121 (S703 Yes → S707). FIG. 26 shows configuration examples of the staff table, job code table, and affiliation code table. Each of the tables is registered in a DB on the campus network, and data on staff is managed. (The database may be dedicated to this system or shared with other campus systems. The latter is more efficient.)

  When it is determined that there is no registration information in the staff table as a result of searching with the name information, a temporary ID is automatically issued (in this embodiment, following “T”, which means a temporary ID) (T00001 "in the example of FIG. 27A), temporary user registration table (FIG. 27A), ID, name, affiliation / job name, employment information (with employment relationship) If it is 1 and 0 if none, contact information is registered (No in S703 → S704). In the subsequent S705, it is determined whether or not there is an employment relationship (information obtained by input to the application application page in FIG. 30). The flag is set to 1 (S706), and the process proceeds to S707. On the other hand, if there is an employment relationship, S706 is skipped and the process proceeds to S707. In S707, an ID (temporary ID issued in S707) is registered in the item of the applicant or the inventor of the corresponding record in the application matter table 11121 (if the processing target is the inventor, the ID and the degree of contribution).

  By executing the above-described processing of S703 to S707 for all applicants and inventors, information on the applicant, inventor, contribution level items, and approval required flag items in the application item table 11121 is registered. . As is apparent from the above, if there is a person who has no employment relationship among the applicant and the inventor in the process, the approval requirement flag is set to 1 (the flag is 0 if all the employees are employees). Becomes). In this embodiment, the input of the applicant is trusted (even if the person is not registered in the staff table, if the input is related to employment, processing based on this is executed. However, by deleting the determination processing in S705, if the person is not registered in the staff table, the manager must be approved (the approval requirement flag is set to 1). Good. Further, in the temporary user registration of S704, a temporary user registration table may be searched based on name information and the like so that duplicate registration is not performed.

  In S708 after the loop processing of S703 to S707, the attached file (technical information file such as a paper) is stored in the application file DB 114, and the stored address information is stored in the material address of the corresponding record in the application matter table 11121. Register in the item. Further, each of the scheduled release date, the name of the invention, the color essential information (1 if the color is essential, 0 if not), the language information, the technical field, the keyword information, and the application information immediately are entered in the application item table 11121. (S709), and the DB registration process is terminated. Note that the language information, the technical field, and the presence / absence of employment relation are as follows: each table (language code table (FIG. 27 (b)), field code table (FIG. 27 (c)), employment code table (FIG. 27 (d)). ) Is stored in the application item table 11121. For items that are not essential input information and no information is input, the item is not stored in the application matter table 11121. In this embodiment, in the process of storing the attached file (technical information file such as a paper), the file name is stored as it is without being changed, but the information of the receipt number is added to the file name. By rewriting, information on which case of the present system may be associated with the file name.

  Returning to FIG. 6 (reception processing by the site for application for paper emergency application), the description will be continued.

  In S608 following the DB registration process of S607 (the process of FIG. 7), the “scheduled release date” obtained as application information is before the date of the application, or the language of the material is other (= Japanese or (If it is not English), and if any of these is true, a page indicating that it cannot be used as shown in FIG. 32 (b) or FIG. 32 (c) is displayed on the researcher PC 121. (S615) and the reception process is terminated. If the publication date is earlier than today (ie, it has already been published), the meaning of filing an emergency paper with this system is limited, so it cannot be used, and the materials are in Japanese or English. If it has not been prepared, it is not possible to apply. (In the current Japanese system, only Japanese or English applications are allowed. Because it is rejected (so-called unacceptable disposal), it cannot be used.

  If the determination in S608 is No, the process proceeds to S609, where it is determined whether the period until the “scheduled release date” obtained as application information is equal to or greater than the reference period, and is determined to be equal to or greater than the reference value. If so, a page urging the user to submit a normal invention notification to a predetermined department is transmitted to the researcher PC 121 (S616), and the acceptance process is terminated. When this system is used as an application to urgently evacuate publicization due to publication of a paper, for example, if there is a grace period of one month or more until the scheduled date of publication, do not apply with this system. However, the automatic generation processing by the present system is not executed, assuming that normal application processing (judgment of whether to apply after submitting a notification of invention or manual creation of application documents) should be performed. The reference period is information set by the administrator and stored in the administrator setting information table 11122 (FIG. 28). The function may be turned off by setting.

  If the determination in S609 is No, the process proceeds to S610, and whether or not the period until the “scheduled release date” obtained as application information is equal to or less than the number of grace days, or is “application immediately”. If it is determined that this is the case, the researcher should display a page as shown in FIG. 32 (d) (a page that displays the reception number and contact information of the person in charge and prompts the person in charge to be contacted). The data is transmitted to the PC 121 (S617), and the process proceeds to S612. The page (FIG. 32 (d)) is automatically generated by inserting the receipt number generated in S701 of FIG. In this system, it is possible to process the application on the day of application (immediately after application), but in the case of a joint application project, adjustments such as obtaining permission from the co-application partner are required (a predetermined period is required for application preparation) In some cases, when there is no predetermined grace period, direct contact with the person in charge (administrator) is urged. In addition, by contacting the person in charge directly, it can be expected that the application will be made with a little margin until the next announcement. The grace period is information set by the administrator and stored in the administrator setting information table 11122 (FIG. 28).

  If all the determinations of S608, S609, and S610 are No (that is, the case where there is no need for a warning corresponding to the period until the “scheduled release date”), the process proceeds to S611 and accepted. A number and a page notifying completion of reception are transmitted to the researcher PC 121. Note that the researcher PC 121 that has received the page transmitted in any one of S615, S616, S617, and S611 displays this (FIG. 5: S510 → S511) and ends the process.

  If the determination in S608 and S609 is No, the process of S612 is executed, and the process returns to the process of FIG. As described above, the information and files necessary for the urgent application for the paper are obtained from the researcher by the process of FIG. 6, and it is not a case that has already been published and is based on the period until the scheduled publication date. The receipt number is obtained as a return value for a case that is not a case that is longer than the period, that is, for a case that an application for this system is permitted. In the present embodiment, it is assumed that the application application page URL is notified only to those who need the application application page, and the login process is not performed. Only the presence or absence is confirmed (FIG. 6: S601), but login may be required when using this system (notifying the person who permits the use of the ID and password in advance). Leave). In this case, access from off-campus may be permitted (the processing of S601 and 618 in FIG. 6 is not performed). As an extreme example, this system is used just before the presentation from the conference venue. It is also possible to apply for an emergency application.) In addition, when the login process is assumed, the applicant information can be obtained from the ID by setting the ID and password for each staff member individually (for example, using the staff member ID). The input of the applicant information can be omitted, and the processing of S703 to S706 in FIG. 7 for the applicant can be omitted. Also for the inventor, input of information such as affiliation, employment relations, and contact information can be omitted by accepting input by staff ID on the application screen of FIG. 30 (contribution information is essential).

  In the present embodiment, for the purpose of constructing a DB related to technical information such as papers, the reception process (FIG. 6) is also requested to input information related to technical fields and keywords. Thus, as described above, the application case table as shown in FIG. 25 is generated by the reception process, and the technical information file such as a paper is associated with the information on the technical field and the keyword. Therefore, a DB that can search for a file such as a paper by a keyword or the like is configured by this system. In this system, it is assumed that not only papers but also various presentation materials are registered. Therefore, the DB can be useful for the activities of the university's intellectual property department and industry-academia collaboration department. If such a DB is not particularly necessary, a system that does not acquire technical field or keyword information at the time of reception processing may be used. In the present embodiment, the process of S607 is performed before the process of S608 and S609 for the purpose of constructing a DB related to papers (therefore, even for a case for which an application for this system is not permitted) However, by executing S607 after these processes, it is possible to register only the cases for which applications in this system are approved in the DB.

<< HTML file automatic generation and storage process: details of the process of S408 in FIG. 4 >>
In S408 of FIG. 4, a process of automatically generating an application HTML file based on the data acquired in the reception process (S405 = FIG. 6) is executed. FIG. 8 is a flowchart showing the processing of S408 in FIG.

  The storage device 1112 of the application file creation support server 111 stores a specification HTML template file (text file) as shown in FIG. The HTML file automatic generation / save process automatically generates an HTML file for application as shown in FIG. 40 using the data acquired in the reception process for the template file. In the specification HTML template file (FIG. 39) in the present embodiment, the identification number, name, representative and prepaid ledger number information of the own institution are described in advance as applicant information. In addition, information is entered in advance for each of the title of the invention, a brief description of the drawing with respect to FIG. 1, claim 1 of the claims, and an abstract. .jpg) is linked. The image file (dummy.jpg) itself is also stored in the storage device 1112 in the same manner as the specification HTML template file.

  The HTML file automatic generation / save process (FIG. 8) is a process corresponding to S408 of FIG. 4, and corresponds to the reception number based on the reception number obtained as the return value of the previous reception process of S405 (FIG. 6). It is processing for the matter to be done. When the HTML file automatic generation and storage process is executed, first, an application reference number is automatically generated, and the application reference number is stored in the application file management table 11123 (FIG. 29) of the storage device 1112 of the application file creation support server 111. Is generated as a primary key (FIG. 8: S801). The application reference number is automatically numbered according to a predetermined rule. In this embodiment, the symbol “E” indicating that the application is an emergency paper and year information (2013 in 2013) Followed by a hyphen and assigning the year's serial number (the number of cases for which an application file has been automatically generated as an application case), the application reference number is automatically generated (accepted in this embodiment) In addition to the application number, an application reference number is assigned separately from the receipt number, and the application reference number is used as the reference number for the application, but the application number is used. It does not matter.) The application file management table 11123 (FIG. 29) is a table for storing information relating to the HTML file for application automatically generated by this system in association with each other. In S801, the receipt number is also registered in the application file management table 11123, and the immediate flag, current day flag, withdrawal flag, warning flag, end flag, and domestic priority flag are initialized to 0 and registered.

  In the subsequent S802, it is determined whether or not the “immediate flag” is “1”. Immediately, the flag is acquired with reference to the application case table 11121 (FIG. 25) using the receipt number as a key. If the flag is immediately 1, the application reference number generated in S801 (hereinafter referred to as “processed application reference number”) is set, with the current date obtained by the date / time function unit from S809 as the expected application date. And stored in the application file management table 11123 (FIG. 29). On the other hand, if the flag is not 1 immediately, the process proceeds to S803, and the date obtained by subtracting the number of grace days from the scheduled release date (obtained from the application case table 11121 using the receipt number as a key) It is stored in the application file management table 11123 (FIG. 29) in association with the processing application serial number. The grace period is information held in the administrator setting information table 11122 (FIG. 28). For example, when the grace period is set to 3 days, the application file management table 11123 stores three days before the scheduled release date as the scheduled application date.

  In subsequent S804, it is determined whether the color flag is 1 or the language flag is 2 (both are obtained from the application item table 11121 using the receipt number as a key), and the color flag is 1 or the language flag is set. If it is 2, the processing of S810 and 811 is executed, otherwise the processing of S805 to S807 is executed. S805 to S807 are processes for automatically generating an HTML file as a normal patent application, and S811 is a process for automatically generating an HTML file as a foreign language document application. When the language flag is 2, since a paper or the like (technical information file attached in the reception process) is created in English, this is a process of generating an HTML file as a foreign language written application. Also, when the color flag is 1, a paper or the like (technical information file attached in the reception process) has been created in color, and the meaning becomes unclear if it is made grayscale. Is to automatically generate an HTML file as a foreign language document application and attach a color PDF file to prevent information loss. (Japanese patent electronic applications are not allowed to attach color images as of 2012, while foreign language documents can be attached with color PDF files. In order to prevent loss of novelty, this system will file an urgent application for dissertation, and will be used for documents that are scheduled to be published. This is the case because an emergency application for a paper with a lack of information may not be able to achieve the goal of preventing loss of novelty.

  Hereinafter, processing for automatically generating an HTML file (S805 to S807) will be described first as a normal patent application, and processing for generating an HTML file (S811) will be described as a foreign language written application.

  In the process of automatically generating an HTML file as a normal patent application (S805 to S807), an application part creation process (S805) that automatically generates an application part using the specification HTML template file, a paper, etc. (in the reception process) A material individual page imaging process (S806) for converting each page of the attached technical information file) into an image file and a specification part creating process (S807) for automatically generating a specification part are executed. In the present embodiment, claims, drawings, and abstracts are set in advance in the specification HTML template file, and the application is made with the content of the template as an example.

<<< Application Form Creation Processing: Details of Processing in S805 in FIG. 8 >>>
FIG. 9 is a flowchart showing the processing operation of the application part generation process. First, in S901, a specification HTML template file (FIG. 39) stored in the storage device 1112 of the application file creation support server 111 is acquired. Next to the flowchart of FIG. 9, the relevant part of the contents of the specification HTML template file is shown, with 1 being the template itself. With respect to the contents of the template file, a processing target application reference number is inserted at a position following the item “reference number” (S902). 2 shows the corresponding part after insertion.

  The loop process following the process of S902 is to repeat the process for the number of inventors, referring to the application item table 11121 (FIG. 25), sequentially acquiring the inventor ID corresponding to the receipt number as a key, The process of S903 is performed on the ID. In S903, based on the inventor ID acquired from the application item table 11121, a name is acquired with reference to the staff table (FIG. 26 (a)), and the name is inserted into “Insert 3” in S903 of FIG. In place of the “inventor” part of the bottom line of the “line”, the three lines are inserted at a position before the “patent applicant” item in the specification HTML template file. The corresponding part after the process is 3 (in this example, there is one inventor. If there are a plurality of inventor IDs in the application case table 11121, the process of S903 is repeated in sequence, and the number of inventor fields is added for the number of persons. ). In addition, when this process is executed, since the inventor outside the university is not included (because this procedure is executed through S407 in FIG. 4), the address of the inventor is that of the institution having this system. An address is set in advance, and this is used.

  As described above, the corresponding part of the specification HTML template file is updated by using the inventor information obtained by the reception process and the serial number automatically generated by the system by the application part creation process of FIG. As a result, the application part is automatically generated. Note that the automatically generated file (a file in which the corresponding part of the specification HTML template file has been updated for this project) is held as a temporary file for later processing.

<<< Document Individual Page Imaging Process: Details of Process in S806 of FIG. 8 >>>
Subsequent to the application part creation process in FIG. 9 (FIG. 8: S805), a document individual page imaging process (FIG. 8: S806), which is a pre-process for creating the specification part, is executed. FIG. 10 is a flowchart showing the processing (processing for converting a file such as a paper into a page (converting into a JPEG file) for each page).

  In the material individual page imaging process, first, a “material address” is acquired from the application item table 11121 using the receipt number as a key, and a technical information file is acquired based on the address information. Next, open the acquired technical information file (execute an application program corresponding to the file (for example, execute Microsoft Word (registered trademark) for a file with the extension .docx)), and issue a print command to the application program. Let it run. Since print output data is obtained from the application program by executing the print command, it is acquired (S1001). That is, in the present embodiment, each application software is installed in the application file creation support server 111, and in S1001, an application program associated with each file format is automatically started by the system, and the application A print command is automatically given to the program.

  In subsequent S1002, the number of pages is substituted for n and 1 is substituted for i based on the print output data obtained by the processing of S1001. As a result, in the loop processing following S1002, the processing of S1003 to 1006 is repeated for the number of pages when the technical information file is printed.

  In S1003, the i-th page is acquired based on the print output data, and the page is converted into a JPEG file (grayscale, 2677 × 4015 dots) (attached as an image to an HTML file for electronic application). Perform possible (allowed) conversion).

  In S1004, a file name is generated by adding an underbar and i after the processing application reference number. For example, when the application reference number is “E2013-001” and the first page is imaged, the file name “E2013-001 — 0001” is generated and the 100th page is imaged Will generate a file name “E2013-001 — 0100”. In the subsequent S1005, the image file is saved in the application HTMLLD 112 with the generated file name, and the address information is stored in the “link file address” of the application file management table 11123 (FIG. 29).

  In S1006, i is incremented and loop processing is continued. When the process for all pages of the print output data is completed (that is, when the loop process is executed until i becomes n), the loop process is terminated. As a result of the loop processing, image files (JPEG files) are generated for the number of pages of the print output data (70 files for 70 pages), and the page number is added to the application application reference number as the file name. Will be given. In this embodiment, a JPEG file is taken as an example. However, any file format may be used as long as it is allowed to be attached as an image to an HTML file for electronic application.

  When the loop processing ends, n is set as a return value (S1007), and the material individual page imaging processing ends.

  By executing the document individual page imaging process (FIG. 8: S806), the technical information file is converted into an image file for each page and stored in the application HTMLDL 112. In the subsequent specification part creation process of S807, a process of generating an HTML file for application is executed using the imaged file and the temporary file generated by the application part generation process. It is to be noted that the specification part creation process (FIG. 8: S807) is executed by using n, which is a return value of the material individual page imaging process (FIG. 8: S806), as an argument.

<<< Specification Part Generation Processing: Details of Processing in S807 of FIG. 8 >>>
FIG. 11 is a flowchart showing the processing operation of the specification part generation process. In S1101, a process of substituting 1 for i is performed. In the subsequent loop processing, the processing from S1102 to S1104 is repeated n times. The n is a return value of the material individual page imaging process (FIG. 8: S806) and corresponds to the number of pages when the technical information file is printed. That is, in the loop processing, the processing from S1102 to S1104 is repeated for the number of pages.

  In S1102, for the specification HTML template file (file in which the application part is updated with respect to the template file) held as a temporary file by the application part creation process (FIG. 8: S805), “Simple Description of Drawing” ”Is inserted at the position before the item, and a line feed tag and a line feed tag with i as the paragraph number are inserted. Next to the flowchart of FIG. 11, a corresponding part in the contents of the specification HTML template file is shown, and 1 is a part of the template itself. The content of 1 → 2 → 3 → 4 is updated by the processing of S1102.

  In subsequent S1103, at the position next to the paragraph number inserted in S1102, a tag for displaying an image is inserted based on the image file of “processing application serial number_i”, and a line feed tag is inserted. “Processing application serial number_i” is the same as S1004 of the document individual page imaging process (FIG. 10), that is, the same as the file name of the image file given in the document individual page imaging process. The file name is generated. Thus, the image file generated for each page in the material individual page imaging process is inserted. By the processing of S1103, the content is updated to the content of 5 (the content of the specification HTML template file next to the flowchart of FIG. 11). In S1104 following S1103, i is incremented, and the loop processing is continued.

By repeating the loop processing of S1102 to S1104 n times, the image file for each page by the material individual page imaging processing is changed to the paragraph number in order from the image file corresponding to the first page. Tags for displaying images one by one are inserted. In this embodiment, i is a paragraph number, that is, the page number and the paragraph number match (paragraph 0001 is the first page image file, paragraph 0002 is the second page image file,. (In the paragraph n, an img src tag based on the image file on the nth page is inserted). Therefore, when the HTML file is viewed on a browser, the first page image of the technical information file is displayed in paragraph 0001, the second page image of the technical information file is displayed in paragraph 0002, and so on. The image file of the nth page is displayed in n. Note that this is done for ease of processing, and is not limited to this, and the paragraph number and the page number may be different.

  In S1105 after exiting the loop process, a process of replacing the paragraph ffff of the specification HTML template file with the paragraph n + 1 is executed. That is, the continuity of the paragraph numbers is maintained by setting the paragraph number of the item “Brief Description of Drawing” as the paragraph number next to n. By the processing of S1105, the content is updated to the content of 6 (the content of the specification HTML template file next to the flowchart of FIG. 11) (here, for the sake of simplicity, an example in which the technical information file has only one page) Become). The specification part generation process ends with the process of S1105.

  As described above, all the pages of the technical information file are pasted to each paragraph number of the specification by the specification part creation processing of FIG. 11, whereby the specification part is automatically generated. In the present embodiment, the claims, drawings, and abstract are set in advance in the specification HTML template file, and the application is made with the content of the template, so S805 in FIG. The HTML file of the urgent paper application is completed by (application part generation processing) to S807 (specification part creation processing). In this embodiment, the application part creation process is processed prior to the document individual page imaging process and the specification part creation process. However, the application part creation process is performed at an arbitrary timing in relation to other processes. (However, as is apparent from the above description, the document individual page imaging process needs to be executed first for the relationship between the document individual page imaging process and the specification part creation process). Further, in the present embodiment, the material individual page imaging process and the specification part generation process are described as separate processes, but the number of loops is common, and the material individual page imaging process and the specification part Instead of separately performing the loop processing of the generation processing, it may be performed simultaneously in one loop.

  Next, the process (FIG. 8: S811) which produces | generates an HTML file as a foreign language document application is demonstrated.

  If the result of determination in S804 (FIG. 8) is that the color flag is 1 or the language flag is 2, the process proceeds to S810. As described above, this processing route is a processing route for generating an HTML file as a foreign language document application. In S810, the symbol “F” indicating that it is a foreign language document application is added at the end of the processing application serial number. By adding, the application reference number is updated and registered in the application file management table 11123 (FIG. 29). For example, when the application reference number generated in S801 is “E2013-001”, it is set to “E2013-001F”, and the information in the application file management table 11123 is updated. Subsequent to S810, foreign document application file generation processing (S811) is executed.

<<< Foreign Document Application File Generation Processing: Details of Processing in S811 in FIG. 8 >>>
FIG. 12 is a flowchart showing the processing operation of foreign document application file generation processing. The storage device 1112 of the application file creation support server 111 stores a foreign language document HTML template file (text file) as shown in FIG. 41, and the foreign document application file generation processing is performed by the template file. On the other hand, an HTML file for application as shown in FIG. 42 is automatically generated using the data acquired in the reception process. In the foreign language document HTML template file (FIG. 41) in the present embodiment, the identification number, name, representative, and prepaid ledger number information of the own institution are described in advance as applicant information.

  In S1201, the foreign language document HTML template file (FIG. 41) stored in the storage device 1112 of the application file creation support server 111 is acquired. Next to the flowchart of FIG. 12, the corresponding part of the contents of the foreign language document HTML template file is shown, with 1 being the template itself. An application reference number (application reference number updated in S810 of FIG. 8) is inserted into the contents of the template file at a position subsequent to the item “reference number” (S1202). 2 shows the corresponding part after insertion.

  Since the loop process following the process of S1202 has the same processing concept as the loop process of FIG. 9, the description thereof is omitted here. The corresponding part after the processing is 3 in FIG.

  In S1204 following the loop processing, “material address” is acquired from the application case table 11121 using the receipt number as a key, and a technical information file is acquired based on the address information. If the technical information file is not a PDF file, processing for converting the file into a PDF file is executed (S1205 No → S1206). On the other hand, if the technical information file is a PDF file, the process skips S1206 and proceeds to S1207. Note that in the conversion process to the PDF file in S1206, the conversion process to the PDF file is executed with the color kept.

  In S1207, the PDF file (technical information file) is saved in the application HTMLDL 112 with the application reference number (the application reference number updated in S810 of FIG. 8) as the file name, and the address information is stored in the application file management table 11123 ( The process of adding to the “link file address” in FIG. 29) is performed. For example, when the application reference number is “E2013-001F”, a file name “E2013-001F.pdf” is assigned and stored in the DB.

  In step S1208, the link destination of the link tag next to the item of “foreign language document” in the foreign language document HTML template file is set as a PDF file (technical information file), and the PDF file name is inserted as anchor text. I do. In the present embodiment, the application HTML file and the PDF file are stored in the same folder, and therefore the file name only needs to be described as the setting of the link destination. For example, when the file name is “E2013-001F.pdf”, the file name is added as a link destination setting to the tag “<a href=“”> </a>”. <A href = “E2013-001F. pdf "> </a>", and by inserting the file name as the anchor text, "<a href =" E2013-001F. pdf "> E2013-001F.pdf </a>".

  Through the foreign document application file generation process, an HTML file for an emergency application (HTML file for application as a foreign language document) is completed.

  In the process of FIG. 12, the technical information file is directly attached to the application as it is (or just converted into PDF and the document format is the original technical information file). In the same way as the processing, create a specification by processing each page of the technical information file and pasting it (FIG. 8: S806 to S807), convert the created specification to PDF and attach it to the application It is good also as processing to do. FIG. 46 is a flowchart showing the processing (the same reference numerals are used for the same processing concept as in FIG. 12). In the processing of FIG. 46, “material individual page imaging processing” is executed following the loop processing. This process is the same as that shown in FIG. 10, but in the conversion process to a JPEG file in S1003, color conversion is performed. The “specification part creation process” following the “material individual page imaging process” is the same process as FIG. 11 except that the template file to be used is an HTML template file other than the application part of the foreign language document. Become. FIG. 44 shows an example of the template file. The HTML file as shown in FIG. 45 is generated by executing the processing of FIG. 11 on the template file. In S1206 (FIG. 46), a process of converting the generated HTML file into PDF without changing the color is performed. Through this process, an HTML file of a foreign language specification (and foreign language patent claims, foreign language summary, foreign language drawing) in which each page of the technical information file is pasted with a color image is automatically generated. A file in which this is converted into PDF in color is generated. In S1208, the PDF file is inserted (linked) into the HTML file of the application as a “foreign language document”.

  Returning to FIG. In S808 after the specification section creation process (S807) or the foreign document application file generation process (S811), the HTML file of the emergency application obtained by each of the above processes, the application application reference number as the file name (for example, "E2013-001F.html") is saved in the application HTMLDL 112, and the address information is added to the "application file address" in the application file management table 1123 (FIG. 29). Further, the generated flag of the application item table 11121 is set to 1 (a flag indicating that the item has been subjected to the automatic generation process of the HTML file). With this, the HTML file automatic generation / save process is completed, and the HTML file (and the image file or PDF file necessary for this) is automatically generated and stored in the HTMLHTML 112 for application. Information relating to the file is stored in association with the application file management table 1123.

  In S409 after the HTML file automatic generation / save process (FIG. 4: S408), if the scheduled filing date (refer to the application file management table 11123) is before today or “immediate flag” (refer to the application item table 11121) is 1. If it is, the immediate process file transfer / notification process is executed (S411).

<< Immediate Process File Movement / Notification Process: Details of Process in S411 of FIG. 4 >>
The immediate process file transfer / notification process is a process of transferring the HTML file for application to a dedicated folder and notifying the administrator, particularly in the case of an urgent matter. A particularly urgent case is a case where the scheduled application date is earlier than today or when the application process is “immediately applied” (at the time of application). In the present embodiment, the scheduled application date is determined based on the scheduled release date obtained in the reception process and the grace date for this (FIG. 8: S803). There is also a possibility. For example, if the grace date is set to 3 days and the scheduled release date is 2 days later, the scheduled application date has already passed 1 day at the time of application. This is to prompt the administrator to pay attention as a matter of immediate application processing. Note that the number of grace days is set as appropriate based on the perspective of how much allowance to file an application with respect to the scheduled release date (according to the operation concept of the organization using this system). FIG. 13 is a flowchart showing the processing operation of the immediate processing file movement / notification processing.

  In S1301, the application file management table 11123 is searched using the processing application reference number as a key, and the application file address and the link file address (if there are multiple files) are acquired.

  In subsequent S1302, based on the address information acquired in S1301, all corresponding files (an HTML file for application and an image file or PDF file based on a technical information file) are acquired from the application HTMLDB 112, and the administrator PC 113 Copy to the folder for immediate processing in the storage unit. The immediate flag of the application file management table 11123 is set to 1. The “immediate processing folder” is a folder set in advance by the administrator, and the setting information is stored in the administrator setting information table 11122 (FIG. 28).

  In S1303, the processing application serial number is mailed to the administrator, and the immediate process file transfer / notification process is terminated. The administrator who has received the notification uses the application software installed in the administrator PC 113 to perform the application process using the application HTML file stored in the “immediate processing folder”. Prompt application procedures are possible.

  As described above, the “acceptance process (FIG. 4: S405, FIG. 6)”, “HTML file automatic generation / save process (FIG. 4: S408, FIG. 8)”, “immediate process file transfer / notification process (FIG. 4 :). S411, FIG. 13) ”, including the processes of S405 to S411, the acceptance of an emergency paper application (including automatic determination of acceptance / non-acceptance) and the availability of automatic processing in the system (necessity of administrator approval) Judgment and automatic generation of an application HTML file by the system are performed.

  Next, a description will be given of a process of copying a file to the processing folder on the day for a case in which the scheduled application date has arrived among the application HTML files automatically generated in S408 (FIG. 4) and stored in the application HTMLDB 112. To do.

<< File Transfer / Notification Process on the Same Day: Details of Process in S414 in FIG. 4 >>
When the “current day file transfer time”, which is a time preset in the administrator setting information table 11122 (FIG. 28), is reached, the current day file transfer / notification process is executed (FIG. 4: S403 → S414). “Same-day file transfer time” is set according to the operation of each institution (for example, if application processing for the day is processed at 17:00 and set at 16:00, For example, it may be possible to move a case for which reception and HTML automatic generation have been completed by 16:00 to a folder for processing that day). FIG. 14 is a flowchart showing the processing operation of the file transfer / notification processing on that day.

  When the file transfer / notification process for the current day is executed, a process for clearing (to 0) all the current day flags in the application file management table 11123 (FIG. 29) is performed as an initialization process. The data for the previous day is cleared. In this embodiment, the file move / notification process is performed on the day, but may be performed in the process of S412 in FIG. 4 (a process of clearing the contents of each folder when the date changes).

  In the loop processing following S1401, the processing from S1402 to S1405 is performed for each of all the records in the application file management table 11123.

  In S1402, it is determined whether the application completion flag is 1 or whether the end flag is 1. If any of them is 1, the processing of S1403 to S1405 is skipped and the processing target Is the next record. For cases that have already been filed (application completion flag = 1) and cases for which application management has been completed in this system (end flag = 1), the processing is excluded from the processing target. In S1403 following S1402, the case where the scheduled filing date is today and the immediate flag is not 1 is determined. If not, the processing of S1404 to S1405 is skipped and the processing target is set as the next record. To do. The case where the scheduled filing date has arrived is determined, and as mentioned above, the case where the immediate flag is 1 is moved to “Folder for immediate processing” separately as a particularly urgent case. Since it is processed, it is excluded from the processing target.

  For a case where the scheduled application date is today (and application completion ≠ 1, end ≠ 1, immediate ≠ 1), the process proceeds to S1404, and the application file address and link file address of the application file management table 11123 (FIG. 29) are set. get. In subsequent S1405, based on the acquired address information, all corresponding files (an HTML file for application and an image file or PDF file based on the technical information file) are acquired from the application HTMLDB 112 and stored in the storage unit of the administrator PC 113. To the same day processing folder. In this process, “dummy.jpg” (an image file set in advance as a template in FIG. 1) stored in the storage device 1112 of the application file creation support server 111 is also processed for the day. Copy to a folder. In addition, the current day flag of the application file management table 11123 is set to 1. The “current day processing folder” is a folder set in advance by the administrator, and the setting information is stored in the administrator setting information table 11122 (FIG. 28).

  When the execution of the processing of S1402 to S1405 for all the records of the application file management table 11123 is completed, the loop processing is terminated, and the management application is assigned a reference number of the application case for that day (in the case of a plurality, a list as a list). ) E-mail to end the file move / notification process on that day. By this file move / notification process on that day, all the files that are scheduled to be filed on that day are stored in a predetermined folder (a folder for current day processing), so the administrator (application processing person in charge) always applies based on the folder. All you need to do is complete the procedure from the software. In this embodiment, all the case files are stored in the same folder as they are. However, each folder with the application reference number as the folder name is automatically generated in the “current day processing folder”, for example. The processing may be such that the file of the corresponding item is stored in the corresponding folder. Further, in the determination process of S1403, by changing the condition of “application date = today” to the condition of “application date is before today”, the case where the scheduled application date has passed but the application has not yet been completed , The file may be moved to the “current day processing folder”.

  If withdrawal management is set after the file transfer / notification process on the day (FIG. 4: S414), the process proceeds to withdrawal confirmation / notification process (S415 Yes → S416).

<< Withdrawal Confirmation / Notification Process: Details of Process in S416 of FIG. 4 >>
Withdrawal confirmation / notification processing is processing for notifying the manager of the arrival of withdrawal time and automatically generating an application withdrawal notice for a case in which a preset period has elapsed after application. FIG. 15 is a flowchart showing the processing operation.

  The storage device 1112 of the application file creation support server 111 stores an application withdrawal document HTML template file (text file) as shown in FIG. In the application withdrawal document HTML template file in the present embodiment, the identification number, name, and representative information of the institution itself are described in advance as applicant information.

  In the withdrawal confirmation / notification process (FIG. 15), a loop process for performing the processes of S1501 to S1505 is executed for each of all the records in the application file management table 11123.

  In S1501, it is determined whether or not the withdrawal flag is 1 or whether or not the end flag is 1. If any of them is 1, the processing of S1502 to S1505 is skipped and the processing target Is the next record. For cases that have already been withdrawn (withdrawal flag = 1) and for which the application management has been completed (end flag = 1), the processing is excluded from the processing target. In S1502 following S1501, the date of the application that has been filed (application completion flag = 1) and the predetermined period from the filing date has passed (withdrawal notification timing: 14 months is taken as an example in this embodiment). The case that is today is determined, and if it does not correspond to this, the processing of S1503 to S1505 is skipped and the processing target is set to the next record. The “withdrawal notification timing” for determining the withdrawal timing is information that is set in advance by the administrator and stored in the administrator setting information table 11122 (FIG. 28).

  For a case where the predetermined period has passed since the filing date (and filing completion = 1, end ≠ 1, withdrawal ≠ 1), the process proceeds to S1503, and the storage device 1112 of the filing file creation support server 111 starts. An application withdrawal document HTML template file (FIG. 43A) is obtained. Next to the flowchart of FIG. 15, the corresponding part of the contents of the application withdrawal document HTML template file is shown, and 1 is the template itself.

  In S1504, “WD” is added to the contents of the template file after the application reference number (the application reference number of the record to be processed in the loop process) at the position following the reference number item. Insert what you did. For example, when the application reference number is “E2013-001”, the reference number “E2013-001WD” is assigned and inserted. Also, an application number (obtained from the record to be processed) is inserted at a position following the application number item. 2 shows the corresponding part after insertion.

  The HTML file of the application withdrawal document automatically generated in S1504, with the application reference number added with “WD” (the same as the reference number added in S1504) as the file name, is stored in the storage unit of the administrator PC 113. The file is stored in the lower folder, and the withdrawal flag of the application file management table 11123 is set to 1 (S1505). The “withdrawal folder” is set in advance by the administrator, and the setting information is stored in the administrator setting information table 11122 (FIG. 28).

  When the execution of the processing of S1501 to S1505 for all the records in the application file management table 11123 is completed, the loop processing is terminated, and the application reference number of the case with the withdrawal flag = 1 & the termination flag ≠ 1 is given to the administrator (multiple If there is, mail is sent as a list and the withdrawal confirmation / notification process is terminated. With this process, a notification regarding withdrawal and an automatic generation process of an application withdrawal document are performed for a case that has been filed and for which a predetermined period has elapsed. The administrator (application processing person) who received the notification will apply based on the files stored in the withdrawal folder as necessary (not necessarily assuming that all cases will be withdrawn). Procedures can be performed from the software.

  Next, a procedure end confirmation process (FIG. 4: S403 → S413) executed when the time reaches the “check time” will be described. This process is a process for confirming whether or not a procedure to be processed (such as an application procedure for an emergency paper application) has been executed.

<< Procedure Completion Confirmation Process: Details of Process of S413 in FIG. 4 >>
The procedure completion confirmation processing in the present embodiment searches the list (CSV file) output from the application software, confirms whether there is information indicating that the procedure has been performed, and when there is no evidence that the procedure has been performed. This is to notify the administrator. That is, in the present embodiment, as a premise of the processing, the administrator performs an operation of CSV file output (in the present embodiment, the CSV format is taken as an example, but not limited to this) by the application software, and a predetermined place (It is set by the administrator and stored in the administrator setting information table 11122 (FIG. 28)) with a predetermined file name (in this embodiment, the application file creation support server 111 The file is stored in the storage device 1112 with the file name “JPOLIST.csv” (the default output file name of the application software). In operation, it is assumed that the procedure processing for the day such as application is performed at a predetermined time (for example, 17:00) every day, and the CSV file output operation is performed by the application software after the processing. Therefore, the “check time” is set at the time when the CSV file output operation is completed. FIG. 16 is a flowchart showing the operation of this processing.

  The processes of S1601 to S1604 are a process for confirming whether or not an application procedure for a case to be filed on that day has been processed (S1601), and a process for confirming whether or not an application procedure for a case to be filed immediately has been performed. (S1602) is a process (S1604) for confirming whether or not a withdrawal procedure has been performed.

<<< Application Case on the Same Day, Procedure Completion Confirmation Process: Details of Process in S1601 in FIG. 16 >>>
FIG. 17 is a flowchart showing the operation of the same day application case and procedure end confirmation processing executed in S1601 of FIG. In S1701, the contents of the unprocessed table on the day are cleared as initialization processing. The unprocessed table on the day is a table in which the application reference number of the corresponding case (unprocessed case on the day) is stored.

  The loop processing following S1701 performs the processing of S1702 to S1707 for each of all the records in the application file management table 11123.

  In S1702, it is determined whether or not the current day flag is 1 and the application completion flag is not 1. If this is not the case, the processing of S1703 to S1707 is skipped and the processing target is selected. The next record. On the other hand, if the case corresponds to the current day flag = 1 and the application completion flag ≠ 1 (that is, the current day application case and the application completion information is not registered), the process proceeds to S1703. In S1703 and S1704, the contents of the “JPOLIST.csv” file in the storage device 1112 of the application file creation support server 111 using the application serial number (the application serial number of the record being processed in the loop process) as a key. And if there is a corresponding record, it is determined whether there is submission date information.

  If there is no record corresponding to the application serial number or the submission date information is not stored in the record, the process proceeds to S1707, and the application serial number is added to the unprocessed table on the current day, and the warning of the application file management table 11123 The flag is set to 1 and the processing target is the next record. On the other hand, as a result of the determination in S1704, if there is a record corresponding to the application reference number and there is submission date information, the process proceeds to S1705, and the corresponding submission date and application number are obtained from the “JPOLIST.csv” file. Then, the acquired information is registered in the application file management table 11123 and the application completion flag is updated to 1. In subsequent S1706, based on the application reference number, a process for deleting all the corresponding files in the processing folder for the day is performed, and the processing target is set as the next record. For cases where it has been confirmed that the application has already been filed by the deletion process, the file will be deleted from the processing folder for that day. When referred to, unnecessary files (processed matters) are not displayed and work efficiency is improved.

  When the processing of S1702 to S1707 is completed for each of all the records in the application file management table 11123, the loop processing is terminated, and the corresponding record is stored in the unprocessed table of the day (ie, “JPOLIST.csv” file). If there is no submission or no record date information is stored in the record, the application reference number list) is returned as the return value, and the current application case and procedure completion confirmation processing is terminated.

  Following the application on the day and the procedure completion confirmation process (FIG. 16: S1601), the immediate application matter and the procedure completion confirmation process are executed (S1602).

<<< Immediate Application Project, Procedure Completion Confirmation Processing: Details of Processing in S1602 in FIG. 16 >>>
FIG. 18 is a flowchart showing the operation of the immediate application case / procedure end confirmation process executed in S1602 of FIG. In S1801, the contents of the immediate unprocessed table are cleared as initialization processing. The immediate unprocessed table is a table in which the application reference number of the corresponding case (unprocessed case) is stored, similarly to the unprocessed table of the day.

  Immediate application case / procedure end confirmation process (FIG. 18) is the same processing concept as that day application case / procedure end confirmation process (FIG. 17) (in terms of whether it is a current day processing case or an immediate processing case). Although the processing concept is the same, the description is omitted here. Note that the warning flag is set to 2 in the processing in S1807. Similar to the application on the day and the procedure completion confirmation process, an immediate unprocessed table is obtained as a return value by this process (S1808).

  Following the immediate application case and procedure end confirmation process (FIG. 16: S1602), it is determined whether or not the withdrawal management flag is 1 (S1603). It is executed (S1604), and if it is not 1, S1604 is skipped. If the withdrawal management is not set, the withdrawal matter and procedure completion confirmation processing is skipped.

<<< Withdrawal Item, Procedure Completion Confirmation Process: Details of Process of S1604 in FIG. 16 >>>
FIG. 19 is a flowchart showing the operation of the withdrawal case / procedure end confirmation process executed in S1604 of FIG. In S1901, the contents of the untreated table are cleared as initialization processing. The withdrawal unprocessed table is a table in which the application reference number of the corresponding matter (unprocessed matter) is stored, similarly to the unprocessed table of the day.

  The withdrawal case / procedure end confirmation process (FIG. 19) is basically the same processing concept as the application case / procedure end confirmation process (FIG. 17), so only the differences will be explained here. A description of the processing is omitted.

In S1902, a case where the withdrawal flag is 1 and the end flag is not 1 (that is, a case that is a withdrawal target matter and has not been finished) is a processing target. In S1903 and S1904, the "JPOLIST.csv" file is searched using the application number as a key, and it is searched whether the procedure name is "Application withdrawal" and there is submission date information. In step S1905, the submission date is acquired and registered in the withdrawal date of the application file management table 11123, and the end flag is set to 1. In the process at S1907, the warning flag is set to 3. As in the case of the application on the day and the procedure completion confirmation process, the unprocessed untreated table is obtained as a return value by this process (S1).
908).

  Following the withdrawal case and procedure completion confirmation process (FIG. 16: S1604), each of the above-mentioned processes (application application day, procedure completion confirmation process (S1601), immediate application matter, procedure completion confirmation process (S1602), withdrawal case Whether or not there is data in each table (current day unprocessed table, immediate unprocessed table, withdrawal unprocessed table) obtained as a return value by the procedure end confirmation process (FIG. 16: S1604)) Whether or not there is a case is determined (S1605), and if there is no unprocessed case, the procedure end confirmation process is ended. On the other hand, if there is an unprocessed matter, an email with a list of all unprocessed matters is sent to the administrator, and the procedure end confirmation process is terminated. In the present embodiment, the immediate application case and the procedure end confirmation process are also described as examples executed at the same frequency as other processes (S1601, S1604). The process may be executed more frequently. Since immediate processing requires quicker processing, the purpose of checking whether or not the procedure has been completed is to be performed more frequently. However, in order to make this an effective process, the file output operation of the application software by the administrator must be performed at a frequency corresponding to that (in this embodiment, there is no program linkage with the application software) However, this does not apply if there is a program linkage).

  Next, a description will be given of processing for performing various settings related to the system, confirmation of each item, information input, and the like by an administrator site that can be operated with administrator authority. This processing is performed by an administrator using the administrator PC 113 to access the application file creation support server 111 (accessing the administrator site using a Web browser and inputting information, etc.) ). In the following, processing on the application file creation support server 111 side will be mainly described (the concept of transmitting / receiving information to / from the application file creation support server 111 using a Web browser is the same as the processing concept of FIGS. 5 and 6). Since this is the same, the description of the processing on the administrator PC side is omitted here).

<< Administrator Operation Process: Details of Process in S417 of FIG. 4 >>
The administrator operation process (S417) is executed by a login operation with a predetermined administrator authority (FIG. 4: access request in S404). The processing includes initial setting by the administrator, approval processing for joint application items, deletion of items, confirmation processing for items that have not been automatically recognized as being processed by the system, and the like. FIG. 20 is a flowchart showing the overall operation of this process.

  First, the administrator top screen generation process for generating the top screen of the administrator site is executed (S2001).

<<< Administrator Top Screen Generation Processing: Details of Processing in S2001 of FIG. 20 >>>
The administrator top screen generation process is a process for generating a top screen for the administrator (FIG. 33 shows an example of the screen). On the top screen of the present embodiment, a list of warning cases (cases for which a warning flag has been set by the processing of FIG. 16), for which information indicating that the procedure period has passed but application has not been obtained, is displayed. It is what is done. FIG. 21 is a flowchart showing the operation of this processing.

  In S2101, the contents of the warning item table are cleared as initialization processing. The warning item table is a table in which information on the warning item list in the top screen shown in FIG. 33 is stored. That is, this is a table in which the application reference number, the reception number, the scheduled procedure date, the application date, the application number, and the warning content information are stored in association with each other.

  Loop 1 following S2101 performs the processing of S2102 to S2103 for each of all the records in the application file management table 11123. In S2102, it is determined whether or not the case is an item for which the immediate flag is 1 and the application completion flag is not 1. If this is not the case, the process of S2103 is skipped and the processing target is changed to the next. Record. On the other hand, if it is a case corresponding to the immediate flag = 1 and the application completion flag ≠ 1 (that is, a case that is an immediate application case and no application completion information is registered), the process proceeds to S2103. In S2103, from the application file management table 11123, using the application serial number (the application serial number of the record being processed in the loop process) as a key, the application serial number, reception number, scheduled application date, application date, application number , And the contents of warning as “immediate application case” are stored in the warning case table. In addition, information on the scheduled application date is stored in the scheduled procedure date of the warning item table. In addition, since not all information exists in the application file management table 11123, “−” is set when there is no information. When the processing of S2102 to S2103 is completed for each of all records in the application file management table 11123, the processing of loop 1 is terminated. The process of loop 1 is to extract a case that is an immediate application case but for which application completion information is not registered from the application file management table 11123 and store it in the warning case table.

  In the subsequent loop 2, the basic processing is the same as that of the loop 1, and the case where the warning flag is 1 and the application completion flag is not equal to 1 (that is, the case where application completion has not been confirmed on the scheduled application date ( 17) and a case in which application completion information is not registered thereafter) is extracted from the application file management table 11123, and this is additionally stored in the warning case table. The contents of the warning are stored in the warning item table as “the filing date has passed”.

  For the subsequent loop 3 as well, the basic processing is the same as in loops 1 and 2, and the case where the warning flag is 3 and the end flag ≠ 1 (that is, the completion of the procedure is not confirmed on the scheduled withdrawal date) Are extracted from the application file management table 11123, and are additionally stored in the warning item table. The scheduled date of the procedure is stored as “the date of application plus a predetermined period (in this embodiment, 14 months is used as an example)” (same as S1502 in FIG. 15). Stored in the alert matter table as “date passed”.

  As a result of the above loop 1 to loop 3, the warning case table first lists “cases that are immediate application cases but have not been confirmed to have completed the application procedure”, and then “the scheduled application date has passed. "Matters for which application procedure completion has not been confirmed" and "Matters for which the scheduled withdrawal date has passed and the procedure has not been confirmed" will be listed. In S2108 after the end of each loop process, a top screen (FIG. 33) is generated based on the warning matter table, and the administrator top screen generation process is terminated (the login operation with the administrator authority has been performed on the screen). This is transmitted to the PC (for example, the administrator PC 113). The same applies to the following). In the determination of S2102, the warning flag (whether or not the warning flag is 2) is not determined, and is determined by the immediate flag. This is because (FIG. 18) is executed only at the check time (FIG. 4: S403 → S413), and there is a possibility that there is an immediate application case to which no warning flag is assigned. Immediate applications are required to be processed as quickly as possible. For cases that have been accepted by the system, those that have not yet been flagged for warning will be listed in the warning case list on the top screen. It is what.

  Returning to FIG. 20, the description will be continued. S2002 to S2005 following the administrator top screen generation process (FIG. 21) in S2001 is a loop waiting for input to the administrator top screen (FIG. 33), and the input (instruction information from the PC based on the operation of the administrator). ), Processing corresponding to this is executed.

  “Approval processing” in the left column of the administrator top screen (FIG. 33) indicates that the administrator confirms with the partner organization, etc. when the inventor is not a follower (a person who is not in an employment relationship). (With the consent to file an emergency application), the system authorizes the execution of an automatic application file generation process by this system. When the “approval process” is selected, the process proceeds to S2006 to execute an administrator approval process (S2002).

<<< Administrator Approval Process: Details of Process in S2006 of FIG. 20 >>>
FIG. 22 is a flowchart showing the operation of the manager approval process. In S2201, the approval case table is cleared as an initialization process. The approval item table is a table in which the information of the approval item list in the approval processing screen shown in FIG. 36 is stored. That is, it is a table in which each information of the reception number, the applicant, the affiliation of the inventor who has no employment relationship, and the scheduled release date is stored in association with each other.

  The loop processing following S2201 performs the processing of S2202 to S2203 for each of all records in the application item table 11121 (FIG. 25). In S2202, it is determined whether or not the case is a case where the approval required flag is 1 and the generated flag is not 1. If not, the processing of S2203 is skipped and the processing target is set as the next record. On the other hand, a case where approval required flag = 1 and generated flag ≠ 1 (that is, a case where the inventor (or applicant) has a person who has no employment relationship, and the HTML file generation process has not been performed yet. If there is no case, the process proceeds to S2203. In S2203, the reception number, the applicant ID, the inventor ID, and the scheduled date of release information are acquired from the application item table 11121 using the reception number (the reception number of the record being processed in the loop process) as a key. . Further, based on the applicant ID and the inventor ID, referring to the staff table (FIG. 26) or the temporary user registration table (FIG. 27), the name information of the applicant and the affiliation information of the inventor who has no employment relationship are obtained. get. Since the “inventor without employment relationship” means that the ID starts with “T” (temporary user ID) and the employment flag is 0, the affiliation information of the person corresponding to this is the temporary user. It is obtained from the registration table. As a result, the information of the reception number, the applicant, the affiliation of the inventor who has no employment relationship, and the scheduled release date are acquired and stored in the approval case table. When the processes in S2202 to S2203 are completed for all the records in the application matter table 11121, the loop process is terminated. In the loop process, a case in which an inventor (or an applicant) has a person who has no employment relationship and an HTML file generation process has not yet been performed is extracted from the application case table 11121, and this is extracted. It is stored in the approval matter table.

  In S2204 after the end of the loop processing, an approval processing screen (FIG. 36) is generated based on the approval case table. Subsequent S2205 and S2212 form a loop waiting for input to the approval processing screen (FIG. 36), and processing corresponding to this is executed according to the input (instruction information from the PC based on the operation of the administrator). It will be.

  When the “confirmation button” corresponding to each item in the approval item list is selected on the approval processing screen (FIG. 36), an individual approval processing screen (FIG. 37) is generated (S2205 → S2206). Information necessary for the screen configuration is obtained from the application item table 11121 (with reference to the staff table (FIG. 26) or the temporary user registration table (FIG. 27)) using the receipt number as a key. In the individual approval processing screen (FIG. 37), the administrator can identify the address of the off-campus inventor and the identification number or address, name, representative name that is information regarding the joint applicant (individual off-campus inventor or the organization to which it belongs). Enter the information (information necessary for filling in the application), and press the “Approve button” if OK. If there is any inconvenience, the “cancel button” is selected.

  In subsequent S2207, input of an “approval button” or “cancel button” on the individual approval processing screen (FIG. 37) is awaited, and if it is cancelled, the process returns to S2204 to continue the processing. On the other hand, if it is approved, the process proceeds to S2208, and an HTML file automatic generation and storage process is executed.

  The HTML file automatic generation / save process executed in S2208 is the same as the process shown in FIG. 8, but in the application part creation process (FIG. 8: S805), the process shown in FIG. 24 is executed. Therefore, only the application part creation process in FIG. 24 will be described here. 24, the same reference numerals are used for the same processes as in FIG. 9, and the description thereof is omitted here.

  After obtaining the specification HTML template file (FIG. 39) stored in the storage device 1112 of the application file creation support server 111 in S901, in S2401, the applicant information is displayed on the individual approval processing screen (FIG. 37). Is obtained (that is, whether or not there is a joint applicant), and if there is not, the following loop processing is skipped. On the other hand, when there is a joint applicant, loop processing is executed.

  The loop process subsequent to S2401 repeats the process by the number of joint applicants, and performs the process of S2402 on the information of each joint applicant obtained on the individual approval processing screen (FIG. 37). In S2402, based on the information on the joint applicant obtained on the individual approval processing screen (FIG. 37), “three rows to be inserted” in S2402 in FIG. 24 is generated (the “acquired information” portion is replaced). The three lines are inserted with a line feed at the position before the “display fee” item in the specification HTML template file. When the process is processed for all joint applicants, the loop process is terminated. As a result, the item “patent applicant” of the application is completed.

  After the loop process, the process proceeds to S902 and the same process as in FIG. 9 is performed. However, in the inventor item insertion process in S903, the address of the inventor who has no employment relationship is displayed on the individual approval process screen (FIG. 37). The information obtained by replacing the information obtained in step) is also used.

  Through the above process (FIG. 22: S2208), the joint applicant information and the off-campus inventor information are added, and then an HTML file for application is automatically generated and stored in the HTMLML 112 for application. Since the processing of S2209 to S2210 after the processing is the same as the processing of S409 → S411 in FIG. 4, the description thereof is omitted here. After the processing of S2209 to S2210, the processing returns to S2201 and continues. As a result, the process is repeated from the generation of the approved case table. However, for the case that has been approved, the generated flag is set to 1 by the HTML file automatic generation and saving process of S2208 (FIG. 8: S808). The determination in S2202 is No, and it is not displayed on the next approval processing screen (FIG. 36).

  When the “delete button” corresponding to each item in the approval item list is selected on the approval processing screen (FIG. 36), the approval requirement flag in the application item table 11121 is set to 0 (S2205 → S2211), Returning to S2201, the processing is continued. Deletion is for suspending the processing in this system in the case where consent to an emergency paper application from an external inventor or the organization to which it belongs is not obtained. Since the approval required flag is set to 0 and the process returns to S2201, the determination in S2202 is No and is not displayed on the next approval processing screen (FIG. 36). As a result, the HTML file automatic generation / save process is not performed for the case. Note that data may be deleted (deletion of data from each table or deletion of a technical information file) for a case for which an application is not filed in this system. Since one object is to construct a DB that can search for files such as papers, it is a process that leaves information for cases that have been submitted to this system.

  When there is a selection of “top” or “setting” in the left column on the approval processing screen (FIG. 36) (request to move to each page) (input waiting loop in S2205 and S2212), The process proceeds to S2213, and the administrator approval process is terminated with the information of “top” or “setting” as a return value.

  As is clear from the series of processes of the administrator approval process, for cases where there is an external inventor, the administrator separately checks with the external inventor and the organization to which it belongs, and the system is based on the confirmation result. By inputting the approval information, the automatic generation process of the application HTML file is executed (or is not executed). Note that even if there is an external inventor, there is not necessarily a joint applicant (it may be a single application after the transfer of the right to receive a patent), so the applicant on the individual approval processing screen (FIG. 37) Information is not a mandatory input item.

  Returning to FIG. 20, the description will be continued. Since “top” or “setting” is obtained as a return value by the administrator approval process (S2006) (FIG. 22: S2213), it is determined which one was obtained (S2007), and “top” was obtained. If so (i.e., if it is a top page display request), the process returns to S2001 to continue the process (i.e., the top page is displayed). On the other hand, if it is “setting”, an administrator setting screen is displayed (S2007 → S2008). FIG. 38 is a diagram illustrating an example of the administrator setting screen. This screen is a screen for performing various settings related to this system. The setting items include “current day file move time (related to the processing in FIG. 4: S403)”, “check time (FIG. 4: processing in S403). ) ”,“ Grace period (used for calculation of scheduled application date, etc.) ”,“ reference period (related to the processing in FIG. 6: S609) ”,“ application file storage folder (storage location of file obtained by reception processing) ) ”,“ HTML file storage folder (storage location of automatically generated HTML file and image file) ”,“ Fast processing folder (temporary storage location of HTML file and image file for application of immediate processing case) ”,“ Same day processing folder (temporary storage location of HTML file and image file for application of the case to be processed on that day) ”,“ withdrawal management (FIG. 4: processing of S415 etc.) (Relationship) ”,“ Withdrawal notification timing (related to the processing of FIG. 15: S1502) ”,“ Removal folder (Temporary storage location of HTML file for procedure of withdrawal case) ”,“ Application software CSV output folder ( The location of the CSV file to be output to the application software).

  The administrator inputs various types of information on the administrator setting screen, and when the necessary information has been input, selects the “Register” button. By selecting the registration button, each input information is transmitted, and the application file creation support server 111 that has received the information performs a process of storing it in the administrator setting information table 11122 (S2009 → S2010). FIG. 28 is a diagram illustrating an example of the configuration of the administrator setting information table 11122. After S2010, the process returns to S2002 and continues the process (returns to the administrator top screen before the administrator setting process shifts and continues the process). If the “Cancel” button is selected on the administrator setting screen, S2010 is skipped and the process returns to S2002 to continue the process (return to the administrator top screen before the administrator setting process is transferred and the process is continued). .

  In the loop waiting for input to the administrator top screen (FIG. 33) in S2002 to S2005, when “Setting” in the left column of the screen is selected (S2003), the process proceeds to S2008, and management is performed as described above. The setting information input by the administrator and the process of storing it in the administrator setting information table 11122 are executed. In the generation process (S2008) of the administrator setting screen (FIG. 38), if setting information is already in the administrator setting information table 11122, a screen in which the information is input is generated.

  When the “processed” button corresponding to the displayed case (warning case) is selected in the loop waiting for input to the administrator top screen (FIG. 33) in S2002 to S2005, the application arrangement of the case is arranged. The processed case registration process is executed using the number as an argument (S2004 → S2011).

<<< Processed Item Registration Process: Details of Process in S2011 in FIG. 20 >>>
The processed case registration process is a confirmation process for a case in which it has not been automatically recognized that the procedure has been completed in the system (a process for inputting the information to the system regarding a case that the administrator has confirmed as having been processed). In the alert case list displayed on the administrator top screen (Fig. 33), select the "Processed" button for the case that has been confirmed to have been processed, and enter the necessary information to register that the procedure has been completed. Is. FIG. 23 is a flowchart showing the operation of the processed case registration process.

  In S2301, a warning flag is acquired by referring to the application file management table 11123 based on the application reference number obtained as an argument, and is determined. If the warning flag is 1 or 2 (that is, a case for which an application schedule has passed), the process proceeds to S2310 to generate an application information input screen as shown in FIG. (Note that even if there is no warning flag, the process proceeds from S2301 to S2310. This is because the warning flag may not be assigned for the immediate processing case.) The application file management table 11123 is generated for generating the application information input screen. This information is obtained from each table of the application information table 11121 and the staff table (and temporary user registration table). The administrator inputs the application date and application number information on the application information input screen (FIG. 34), and selects the “Register” button. As a result, the input application date and application number information are transmitted to the application file creation support server 111, and the application file creation support server 111 that has received them stores them in the application file management table 11123, The completion flag is set to 1 (S2311 → S2312).

  When the registration process of S2312 is completed, the process proceeds to S2309, and the registered case registration process is terminated with “registration” as a return value. If the “Cancel” button is selected on the application information input screen (FIG. 34), the processed case registration process is terminated with “Cancel” as a return value (S2311 → S2313).

  As a result of the determination in S2301, if the warning flag is 3 (that is, the case for which the withdrawal period has passed), the process proceeds to S2302, and a withdrawal information input screen as shown in FIG. 35 is generated. The withdrawal information input screen is also generated by obtaining information from the application file management table 11123 information, the application matter table 11121, and the staff table (and temporary user registration table). On the withdrawal application information input screen (FIG. 35), the administrator inputs the withdrawal date or priority claim application number information and application date information based on the case, and selects the “Register” button.

  When the “Register” button is selected, the input information is transmitted to the application file creation support server 111. Upon receiving this, the application file creation support server 111 determines whether there is information on the priority application (S2303). → S2304). If there is this, it is determined whether or not the priority application is a domestic priority claim application or a PCT application (a case that is regarded as a domestic priority application designated by Japan) (S2305) and is given priority in Japan. If it is a case, the domestic priority application number (or the application number of the PCT application including Japan in the designation) and the application date information are registered in the application file management table 11123 (in FIG. 29, information on the priority application is displayed). The input field is omitted), and the domestic priority flag and end flag are set to 1 (S2314). The application based on the domestic priority (emergency paper application) is automatically deemed to be withdrawn after the lapse of one year, and the management of this system will be terminated. After S2314, the process proceeds to S2309, and the registered case registration process is terminated with “registration” as a return value.

  As a result of the determination in S2305, if the case is not a domestic priority case (if it is just a Paris priority case), the application number and application date information of the priority claim application are registered in the application file management table 11123 (S2306), It is determined whether or not withdrawal date information is input (S2307). If there is withdrawal date information, it is registered in the application file management table 11123, and the end flag is set to 1 (S2308). After S2308, the process proceeds to S2309, and the registered case registration process is terminated with “registration” as a return value. On the other hand, if there is no withdrawal date information, “cancel” is set as a return value, and the processed case registration process is terminated (S2307 → S2313). In Paris priority, only the basic application (thesis urgent application) is not withdrawn, so it is confirmed whether it has been withdrawn separately, and if there is no withdrawal information, it will continue to be managed as “a project whose withdrawal period has passed” To do.

  If there is no information on the priority application as a result of the determination in S2304, the process proceeds to S2307 and the above processing is executed (if there is withdrawal date information, various information is registered and “Register” is set as the return value. For example, “Cancel” is used as the return value to finish the processed matter registration process). Even when the “cancel” button is selected on the withdrawal application information input screen (FIG. 35), the processed case registration process is terminated with “cancel” as a return value (S2303 → S2313).

  Through the above processed case registration process, “registration” or “cancel” is acquired as a return value. Returning to FIG. 20, the description will be continued. In S2012 after the processing (FIG. 20: S2011), it is determined whether the return value is “registration” or “cancel”. If it is registration, the process returns to S2001 to return to the administrator top screen. Is regenerated. On the other hand, in the case of cancellation, the administrator top screen is not regenerated, and the processing is continued by returning to the administrator top screen before shifting to the processed matter registration processing. In the processed matter registration process, if information indicating that the procedure has been completed is obtained, the matter is no longer subject to warning, so the administrator top screen is regenerated, but the completed information is obtained. If not, the process is continued with the previous warning item list.

  When “END” in the left column of the administrator top screen (FIG. 33) is selected, the administrator operation process is ended (S2005). On other screens such as the approval processing screen, an end button may be provided, and when this is selected, the administrator operation processing may be ended. In addition, a case search column is provided at the top of each screen such as the administrator top screen (FIG. 33), and a case corresponding to the information input here is searched by referring to each table, and the search result is displayed. An item search function such as displaying in a separate window may be provided.

  The processing concept of the application support system according to the present embodiment has been described above. As is clear from these, according to the application support system of this embodiment, for example, in a research institution such as a university, a researcher uploads a technical information file such as a paper to a predetermined site, so that the paper (technical information) File) is automatically generated from the file and automatically saved in a predetermined folder on the application date. For the researcher (inventor), the work is simply to upload the paper to the specified site. Also, the person in charge of the intellectual property department etc. applies the HTML file for application saved in the specified folder with the application software. Therefore, simple and quick processing is possible for both the inventor and the person in charge of intellectual property.

  In addition, according to the application support system of the present embodiment, application software associated with each file format (for example, Microsoft Word (registered trademark) for a file with an extension of .docx) is started, and the software Print output data is obtained using the print function of this, and conversion processing to an image file is executed based on the print data. Therefore, even if the technical information file (electronic file such as a paper) is in various formats, it is uniform. Since the automatic generation process of the specification can be executed by a typical process, the versatility is high and the convenience for the user is also high.

  In addition, if an inventor who is not an employee (a person who does not have an employment relationship) is included, it is required to enter the administrator's approval information for automatic processing in the system, and the occurrence of an unapproved application should be suppressed. Can do.

  Furthermore, in the reception process, an input as to whether or not the information cannot be accurately transmitted unless the technical information file is in color is received. If the technical information file is indispensable in color, automatic generation of the application HTML file is performed. Since this is automatically generated as a foreign language document and the technical information file is attached in color as a PDF file, the loss of information is suppressed.

  In the present embodiment, the description is made on the assumption that the item of the title of the specification, the contents of claim 1 of the claims, and the means for solving the abstract remain as templates. If the name of the invention can be acquired in the reception process, the information on the item of the name of the invention in the description, the contents of claim 1 of the claims, the part of the abstract solution means It is good also as the process which replaces with a model. In addition, by inputting more information (claim contents and summary contents) in the reception process, it may be used for the automatic generation process of the application HTML file, but the input information is increased. As the burden on the researcher increases, there is a trade-off with the original purpose of the system.

  Although this embodiment has been described as a patent application, a utility model registration application can also be processed using the same processing concept. In addition, the explanation has been made on the assumption that a Japanese patent application is applied, but it is also possible to automatically generate a PCT application, and in other countries, the processing concept of the present invention is applied corresponding to each application system. It is possible.

  In this embodiment, the automatically generated HTML file for the application is temporarily stored in the same location (application HTMLHTML), and the matter corresponding to the scheduled application date is moved (copied) to the folder for processing on the day. Although described as an example, folders corresponding to the scheduled application date (for example, folders with a date (such as “20130101”) as the folder name) are automatically generated or prepared in advance, and the corresponding folder is applicable to the date folder. It may be configured to store a file of matters of application date. As a result, the administrator performs the application procedure based on the files in the date folder corresponding to the current day.

  In the present embodiment, the process of automatically generating an HTML file (FIG. 4: S408) is taken as an example after reception, but the execution timing of the automatic generation process is not limited to this, and the scheduled filing date Anything that is executed by (more precisely, scheduled date and time) may be used. For example, the automatic generation processing is not performed at the time of acceptance, and the HTML file automatic generation processing of the corresponding case is executed on the scheduled application date, or the processing on the reception day is batch processed on the night of the reception day. Good (however, immediate processing matters need to be processed immediately).

  In the present embodiment, each template file is a text file, and after adding or replacing a part of the contents, a process of saving as an HTML file (automatically generating an application HTML file) has been described. A template file may be handled as an HTML file, or a template may be prepared in a file of another format and finally converted to HTML.

  In this embodiment, the number of grace days is set, and the date obtained by subtracting the number of grace days from the scheduled release date is used as the application scheduled date, but the application acceptance date is used as a reference instead of the scheduled release date. As a matter of course, the filing date may be determined (however, as a matter of course, the filing date needs to be earlier than the publication date). In addition, in the reception process, it may be possible to obtain an application scheduled date instead of the scheduled release date, and process based on this (in this case also, it is necessary to ensure that the date is before the publication date). is there).

  In this embodiment, in the reception process, input of information indicating whether color is essential is requested, and an HTML file is generated in a foreign language document based on the input information (FIG. 8: S804). → S810 ・ 811), instead of asking the applicant for information on whether or not color is essential, it is automatically determined whether or not the technical information file is in color. Alternatively, the HTML file may be automatically generated in a foreign language document. (For example, it is determined whether or not the color is based on the print output data obtained in the “material individual page imaging process” in the present embodiment, and if it is a color, the process proceeds to S810 and 811).

In addition, as long as the processing concept is the same as that described above, a difference in hardware configuration or the like is not a problem. For example, although it is described as a CPU or the like, it does not mean that all programs are executed by the same CPU, and may be distributedly processed by a plurality of CPUs (or GPUs). There is nothing to say that they must be in the same enclosure. In the above description, some or all of the functions realized by software may be configured in hardware, or vice versa.
Further, the configuration of each table is an example for explanation, and it is sufficient that each information is associated (directly or indirectly associated) in a form in accordance with the concept of the present invention understood from the above description ( Naturally, the DB is appropriately normalized and the like). The same applies to the following embodiments.

(Embodiment 2)
The service provider having the application support system according to the second embodiment is a service provider who, for example, uses an institution such as a university as a customer, receives a technical information file such as a paper from the university, and submits an emergency application for the paper. Yes (that is, the service provider of the application support system is a patent attorney or a patent business corporation because it acts as an application agency). At the same time, another agent (patent office) is also a customer (service provision target), and if the university wants to create a draft claim related to an emergency paper application, the contents of the technical information file etc. will be transferred to the agent side (service A service that allows customers (universities, etc.) to confirm the proposed claim by presenting it to another agent who is not the provider), and the agent who receives it creates a proposed claim and registers it in the system. Provided (mediation business). An emergency paper application is a procedure to prevent loss of novelty, and in order to obtain useful rights, a priority application is usually required, so it is possible to select an agent for that application. On the other hand, the agent side (other agents who are not service providers) can also obtain an opportunity to obtain a new job request. Furthermore, in the application support system of the second embodiment, an evaluation for a patent attorney (or patent engineer) is given, and a service for providing this is also possible.

  FIG. 47 is a block diagram showing an outline of an application support system according to the second embodiment. Constituent elements similar to those in the first embodiment (FIG. 1) are denoted by the same reference numerals as those in the first embodiment, and description thereof is omitted here. As shown in the figure, a trader system 470, a customer PC 479 that is an information processing device used by a customer (university, etc.), and a patent office that is an information processing device used by an agent who is the other customer. The PC 478 is a constituent element. The supplier system 470 includes a customer file DB 472, an application file creation support server 471, and the like. The application file creation support server 471 is not particularly different in hardware from that of the first embodiment, but there are portions that are different from those of the first embodiment in terms of function, and will be described below. In addition, each program, table, and the like different from those in the first embodiment are provided to realize the function. According to each hardware resource such as CPU and each program, each function processing unit (login processing unit, technical information file acquisition unit, application generation unit, specification automatic generation unit, application file generation unit, file imaging unit, technical information file The same concept as that of the first embodiment is configured such that the presenting unit, the complaint plan acquisition unit, the complaint plan presentation unit, the agent evaluation information acquisition / presentation unit, the application request reception / notification processing unit, and the billing processing unit) are configured. is there.

  In this embodiment, a person who has been registered in advance for both the university and the agent side is the object of service provision, and the customer who uses the emergency paper application service such as the university is configured as shown in FIG. In the customer table 5901 as shown in the example, in addition to the ID and password as login information, the name, address, person in charge name, contact information (phone number, etc.), e-mail address, account information (billing information) Information), an identification number (identification number in the Patent Office), a representative name, and the like are stored in association with each other. On the agent side, as office information, the office table 5902 (shown in FIG. 59 (b) shows a configuration example), ID, name, address, mail address, telephone number, FAX number, account information (billing) And the like) are stored in association with each other. In addition, on the agent side, information as an individual patent attorney is also registered. In the patent attorney table 5903 as shown in FIG. 59 (c), the information includes an ID and password as login information, a name, an e-mail address, a telephone number, a FAX number, and an ID of the office to which the user belongs. , Information such as information on technical fields that can be handled is stored in association with each other (not necessarily a patent attorney but may be a so-called patent engineer). The customer table 5901, the office table 5902, and the patent attorney table 5903 are stored in the customer file DB 472.

<Overview of application file creation support server overall processing>
An overview of the entire processing operation in the application file creation support server 471 of the present embodiment will be described, and thereafter, each functional process constituting the entire process will be sequentially described in detail. FIG. 48 is a flowchart showing an outline of the overall operation of the application file creation support server 471, and the outline of the processing operation of the application file creation support server 471 will be described based on this flowchart.

  S4801 to S4803 form a loop for waiting for the occurrence of an event, and processing corresponding to the event is executed according to the occurrence of each event.

  When there is a login request to the system from the login screen of a predetermined site that provides the service by this system (S4801), the university or the like receiving the service for urgently applying for the paper (hereinafter simply referred to as "customer") Whether the login request is a login request based on the individual patent attorney (or patent engineer individual) ID (S4804). The login authentication and the determination of S4804 are performed with reference to the customer table 5901 (FIG. 59A) and the patent attorney table 5903 (FIG. 59C). If the password does not match, login will be refused). If the logged-in user is a customer, the process proceeds to S4805 to execute “customer-facing site processing”, whereas if the logged-in person is a patent attorney, the process proceeds to S4806 to execute “office-compatible site processing”. To do. “Customer-facing site processing” is processing for providing services such as urgent paper application services to customers, and “Office-facing site processing” requested patent attorneys to create complaints from patent attorneys. This is a process for presenting a case and inputting a draft proposal for the case.

  In the loop processing of S4801 to S4803, when the time has reached midnight, “current case application processing” is executed (S4802 → S4807). “On-the-day case application processing” executes application processing of a case (thesis emergency application) on the scheduled application date. In the first embodiment, the application process by the application software has been described as an example of manual processing. However, in the present embodiment, the application software is automatically started by the system and the application process is automatically performed as an example. .

  In the loop processing of S4801 to S4803, when the time is 11:00 pm (S4803), "withdrawal processing (S4808)", "procedure end notification processing (S4809)", and "billing processing (S4810)" are executed. To do. The “withdrawal process” executes a withdrawal procedure for a case for which a withdrawal date has arrived when a customer requests withdrawal of an emergency paper application on a predetermined date. “Procedure completion notification process” is a process for notifying the completion of the procedure and sending the procedure documents, etc., for the matters that have undergone the procedure (application procedure, withdrawal procedure) on that day. Based on this, the customer or patent attorney is charged. In this example, the “application process for the current day” is executed at midnight (that is, at the same time as the date changes), and the “withdrawal process” is executed at 23:00 as an example (the application is withdrawn as soon as possible. However, the timing of the processing may be arbitrarily set.

  The above is the outline of the entire processing operation in the application file creation support server 471. Hereinafter, each functional process constituting the overall process will be sequentially described in detail.

<< Customer Response Site Processing: Details of Processing in S4805 of FIG. 48 >>
When there is a login request from a customer, customer-facing site processing is executed (FIG. 48: S4804 → S4805). FIG. 49 is a flowchart showing the processing operation of the customer service site processing.

  First, in S4901, processing for generating a customer site screen as illustrated in FIG. 65 is executed. The top page of the customer site presents a list of paper emergency application cases requested by the logged-in customer, and buttons such as correction and evaluation are assigned to each case on the right side of the list. Regarding the generation of the list (acquisition of “reception number”, “scheduled application date”, “application date”, “application number”, “patent office staff” in the list), first, an application matter table 6001 (FIG. 60) based on the applicant ID (= login ID), the corresponding case (thesis emergency application case requested by the logged-in customer) is extracted, and each table ( This is performed by obtaining necessary information with reference to the application case table 6001 (FIG. 60), the application file management table 6101 (FIG. 61), and the patent attorney table 5903 (FIG. 59 (c)). The correction button is assigned to the extracted cases where the end flag is not 1 (see the application file management table 6101), and the assignment of the evaluation button is the case with the data of the patent office staff (application file management) It is assigned only for the patent number corresponding to the record of the corresponding receipt number in the table 6101 (FIG. 61). In the remarks column, when there is a record of the corresponding receipt number in the complaint plan table 6401 (FIG. 64), the display “there is a complaint plan” (the complaint request flag in the application matter table 6001 (FIG. 60) is 2). In this case, “represented by proxy” is displayed), and when the withdrawal flag in the application file management table 6101 (FIG. 61) is 1, “withdrawn” is displayed. When there is information (application number), the information and “priority claim application completed” are displayed. In addition, the display of the remarks column is not displayed exclusively, and when there are a plurality of items, they are listed and displayed.

  S4902 to S4905 after the top screen display process (S4901) is a loop waiting for the occurrence of an event (customer operation on the top screen), and a process corresponding to this is executed according to the customer operation. It will be.

  “Application request” in the left column of the top screen (FIG. 65) is for accepting a request for an emergency paper application, and when the item is selected, an acceptance process is executed (S4902 → S4906).

<<< Reception Processing: Details of Processing in S4906 in FIG. 49 >>>
FIG. 50 is a flowchart showing the processing operation of the reception process in this embodiment, and corresponds to the process of S4906 in FIG. Components having the same processing concept as the reception processing (FIG. 6) of the first embodiment are denoted by the same reference numerals, and description thereof is omitted here.

  The paper emergency application application page generated in S602 is the page shown in FIG. 66 in the present embodiment. Compared to the first embodiment, there is no input of applicant information, but instead of input of applicant information, there is no input of information regarding employment relations. Further, the present embodiment is different from the first embodiment in that the application date (desired date) is input, and information regarding withdrawal and information regarding creation of a complaint are input. Regarding the applicant information, in the present embodiment, since the service is used through a login process by a customer registered in advance, it is not necessary to input the applicant information. In addition, since the applicant information can be acquired from the registration information (customer table 5901 (FIG. 59 (a))), the corresponding information is input in advance and the screen is configured (the customer selects the information as necessary). Correction and additional input of the applicant). For information on employment relations, the customer is responsible for processing the right to receive a patent, and the service provider is not involved in this (the contract conditions for service provision), so input is unnecessary. Yes. In the first embodiment, the scheduled release date is input and the application is filed a certain period before that date, but in this embodiment, the desired application date is directly input. It also asks for input regarding whether or not to withdraw the urgent application for papers (if so, specify the timing of withdrawal) and whether to request a draft proposal from the patent office (details will be described later). .

  In S5001 (FIG. 50) after the process for generating the paper emergency application application page (FIG. 66), the user waits for the “confirm input contents” button or the “cancel” button to select the “confirm input contents” button. Thereafter, the processing is basically the same as in the first embodiment (FIG. 6). The difference from the first embodiment (FIG. 6) is that the DB registration process (S5002) of the present embodiment is simply a process of registering the received information in the application item table 6001. FIG. The approval flag is not set as in the above process. Further, the process (S609 → S616 in FIG. 6) when the period until the application date (the publication date in the first embodiment) is equal to or longer than the predetermined period is not performed.

  Returning to FIG. 49 (customer response site processing), the description will be continued.

  In S4907 after the reception process, it is determined whether or not there is a reception number as a return value from the reception process. If there is no reception number (if the application date is earlier than the reception date or the application is not possible or has been canceled) ), The process returns to S4901 to continue the processing. On the other hand, if there is a receipt number, HTML file automatic generation and storage processing is executed (S4907 → S4908).

<<< HTML File Automatic Generation and Saving Process: Details of Process in S4908 of FIG. 49 >>>
In S4908 of FIG. 49, a process of automatically generating an application HTML file based on the data acquired in the reception process is executed. FIG. 51 is a flowchart showing the processing of S4908 in FIG. The same reference numerals are used for the same processing concept as in the first embodiment (FIG. 8), and the description thereof is omitted here.

  In S5101, a new record is generated in the application file management table 6101 (FIG. 61) based on the receipt number. In the first embodiment, the application reference number is generated separately. However, in this embodiment, the receipt number is used as it is. The processes in S804 to S811 are the same as those in the first embodiment. Note that since the generation flag is not used in the present embodiment, processing relating to the generation flag is not performed in S5102.

  Returning to FIG. 49 (customer response site processing), the description will be continued.

  In S4909 after the HTML file automatic generation and storage process, it is determined whether the application request date of the case accepted in the acceptance process is today or whether it is an immediate application case. If this is not the case, It returns to S4901 and continues processing. On the other hand, if the desired application date is today or if it is an immediate application, the application process is executed (S4909 → S4910). As described above, in this embodiment, the application software is automatically activated by the system, and the application process is automatically performed. That is, the application software is controlled based on the API of the application software, and the application process is executed using the application file generated and stored in S4908. In S4910, the application information (application number and application date) obtained after the application processing is acquired, the information is recorded in the corresponding record of the application file management table 6101 (FIG. 61), and the application completion flag is set to 1. Also, the application software outputs the receipt and the proof file (outputs the HTML converted file), stores it in the DB, and records the address information of the file in the application file management table (in FIG. 61, the proof file The address information item is omitted). Further, a record with the receipt number as a key is generated in the accounting table 6201 (FIG. 62 (a)), the procedure type code is set to 1, the application date, the ID of the customer who has logged in to the billing destination, and the settlement flag Record 0 in each.

  By the processing in S4906 to S4910, the request for the emergency paper application from the customer is received, and the automatic generation of the application file (and the application processing when the application is immediately filed) is performed.

  In the loop waiting for operation on the top screen (FIG. 65) in S4902 to S4905, when a correction button is selected, individual case detailed information registration processing is executed (S4903 → S4911).

<<< Individual Item Detailed Information Registration Processing: Details of Processing in S4911 in FIG. 49 >>>
When there is a request for correction of registration contents for a requested matter from a customer, individual matter detailed information registration processing is executed. FIG. 52 is a flowchart showing the processing operation of the individual item detailed information registration processing.

  In S5201, it is determined whether the application completion flag is 1 with reference to the application file management table 6101 (FIG. 61) based on the receipt number of the case for which the correction button has been pressed. In S5208 to S5210, the process proceeds to S5202 to S5207 if the application has not been filed. If the application has been filed, the information for the application (information such as the filing date) has been finalized (some of which can be changed by the change procedure to the Patent Office, such as the applicant). This information is not to be arbitrarily changed in this case), so that information cannot be amended, and if it has not been filed, we can accept the withdrawal of the request for an emergency paper application, In some cases, the request itself cannot be withdrawn, so the processing is divided depending on whether or not the application has been filed. In the present embodiment, the processing as described above is taken as an example. However, information on applicant information after application may be corrected.

  If it is determined in S5201 that the case has not been filed, the process proceeds to S5202, and unapplied matter information correction processing is executed.

<<<<< Unapplied matter information correction processing: details of processing in S5202 in FIG. 52 >>>>
In S5202 of FIG. 52, an unapplied matter information correction process, which is a process of accepting correction of registration information for a requested case that has not yet been filed, is executed. FIG. 53 is a flowchart showing this processing. Note that the same reference numerals are used for the same processing concept as the reception processing in FIG. 50, and description thereof is omitted here.

  In S5301, an information correction page as shown in FIG. 69 is generated. The information correction page is basically the same as the request page (FIG. 66), but the correction page does not have an entry field for the planned release material, and changes to the planned release material are not accepted (in this embodiment, no change is made to the material). (For example, it is not possible to replace, but it may be allowed to be replaced.) In addition, the screen is configured to display the registered contents.

  In step S5302 and S5001, input from the customer to the screen is awaited. If an application cancel button is selected, the process proceeds to step S5305, where an application file (generated based on a template is generated using the receipt number as a key). The generated HTML file and each image file generated based on the material (technical information file) are deleted, and the end flag of the application file management table 6101 (FIG. 61) is set to 1. After the processing, the unapplied matter information correction processing is terminated, and the processing returns to the individual matter detailed information registration processing.

  On the other hand, when the registration button is selected (when the registration button is pressed after inputting correction of information), the information is registered in the same process as in FIG. 50 (however, the corrected application date information is today). If it is earlier, correction is impossible (S5303 → S615). In S5304 after the information registration process (S5002), it is determined whether the correction contents are “technical field”, “keyword”, “withdrawal”, or “claim request”. Then, the subsequent process is skipped and the unapplied matter information correction process is terminated (the receipt number does not become a return value). On the other hand, if the determination result in S5304 is negative, the processing from S610 is executed, and the unapplied matter information correction processing is terminated with the reception number as a return value.

  Returning to FIG. 52 (individual item detailed information registration processing), the description will be continued.

  When the receipt number is obtained as a return value by the unfiled matter information correction process (S5202), a process for deleting the application file is executed using the receipt number as a key (S5203 → S5204), and an HTML file is automatically generated. A saving process is executed (S5205). Since the processing of S5205 to S5207 is the same as the processing of S4908 to S4910 in FIG. 49, description thereof is omitted here. The processing of S5202 to S5207 corrects the registered contents for the requested case before the application, and if there is a change related to the application file, the application file regeneration process is executed (application) If there is a change related to the file, the receipt number is obtained as the return value of the unfiled matter information correction process, and the HTML file automatic generation / save process is executed).

  As a result of the determination processing in S5201, if the correction button is pressed for a file that has been filed, a correction page for the filed file as shown in FIG. 68 is generated (S5208). As mentioned above, since information such as the filing date has been finalized, these cannot be corrected, and “technical field”, “keyword”, “withdrawal”, “claim creation request”, “priority claim application” The application number and application date information ”and“ person-in-charge information ”can be corrected or newly registered. “Application number and filing date information of priority claim application” is the input of the priority claim application when a priority claim application (domestic or PCT, foreign application) based on the urgent application for the paper has been filed. It is what makes you. The person-in-charge information is patent attorney information handling the priority application.

  In step S5209 subsequent to step S5208, the process waits for input of a registration button or a cancel button on the screen of FIG. 68, and in the case of registration, processing for registering the obtained information in the table is performed (S5210). In the registration process, for “technical field”, “keyword”, “withdrawal”, and “claim creation request”, the corresponding information in the application case table 6001 is updated, and “information on priority claim application”, “person in charge information” is updated. ", The corresponding information in the application file management table 6101 is updated. In this processing, when “information on priority application” is obtained and this is a domestic priority application, the end flag of the application file management table 6101 is set to 1 (the basic application of the domestic priority application is (Because it will be disregarded). If the result of determination in S5209 is cancellation, S5210 is skipped and the individual item detailed information registration process is terminated.

  Returning to FIG. 49 (customer response site processing), the description will be continued.

  When an evaluation button is selected in the loop waiting for operation on the top screen (FIG. 65) in S4902 to S4905, processing for generating an evaluation screen as shown in FIG. 72 is performed (S4903 → S4912). The evaluation screen is a screen for inputting the customer's evaluation for the patent attorney (or patent engineer). In this embodiment, “claim creation ability”, “specification creation ability”, “intermediate processing ability”, “rapid” An example is an item that evaluates each item of "sex", "office work", "price", and "cost performance" in five stages. In addition, text is freely entered as a comment. As shown in FIG. 65, assigning an evaluation button only to a case where patent office staff data exists (the patent number corresponding to the record of the corresponding reception number in the application file management table 6101 (FIG. 61)). It will be an assessment of the patent attorney. On the evaluation screen (FIG. 72), information on patent attorneys to be evaluated (information acquisition from patent attorney table 5903 (FIG. 59 (c)) and office table 5902 (FIG. 59 (b))) is displayed in the left column. The upper column displays a graph of the patent officer's previous evaluation, and the lower column is an input column for the above-mentioned evaluation items. In the graph in the upper column, the left side is a graph corresponding to each evaluation item, and the right side is an evaluation graph for each technical field. For the left graph, by taking the average value of records extracted from the evaluation table 6301 (FIG. 63) based on the patent attorney ID, the evaluation value of each item of the patent attorney is calculated and graphed. For the overall average value (dotted line in the figure), the average of all records is graphed. For the graph on the right side, the records extracted based on the patent attorney ID from the evaluation table 6301 (FIG. 63) were averaged by adding the claim creation ability, description creation ability, and intermediate processing ability for each technical field code. Depending on the object (which item is to be evaluated may be selected as appropriate), a graph is formed. Since the technical fields that can be dealt with by patent attorneys are usually limited, the evaluation values are usually limited only to the fields that can be dealt with by the patent attorneys. Here, a simple average is used as an example, but calculation of numerical values may be performed by applying various statistical methods.

  If the send button is selected after inputting an evaluation item on the evaluation screen, the process proceeds to S4914 (FIG. 49) and the acquired information is received in the evaluation table 6301 (FIG. 63). A new record is generated and registered using the number as a key (if there is a record with the corresponding receipt number, the record is updated). As shown in FIG. 63, the evaluation table 6301 includes a reception number, a technical field code acquired from the application case table 6001 (FIG. 60) using the reception number as a key, and each evaluation information acquired through the evaluation screen. Consists of. After the process of registering information in the evaluation table 6301 (S4914) or when the return button is selected on the evaluation screen (S4913), the process returns to S4901 to continue the process. In this embodiment, each case and the evaluation for each patent attorney (individual) are recorded in association with each other. However, the evaluation is accumulated for each patent attorney (the association with the case is eliminated). However, it may be assigned to each office instead of individual patent attorneys. Further, depending on the evaluation item, the personal assignment and the office assignment may be separated (for example, information such as “office work”, “price”, “cost performance” is recorded as an office evaluation) Such).

  In the loop waiting for operation on the top screen (FIG. 65) in S4902 to S4905, when “There is a complaint plan” is selected in the remarks column of the project list, a complaint plan display process is executed (S4904 → S4915).

<<< Claim Plan Display Process: Details of Process in S4915 of FIG. 49 >>>
If the customer has requested a draft proposal when requesting an emergency application (or later amendment), the system will present the relevant paper (technical information file) to the patent attorney. (The patent attorney registered in the system is in a state where it can be browsed), and a draft claim from the patent attorney is input to the system (details will be described later). If the patent attorney has registered a complaint, the message "There is a complaint" is displayed in the corresponding item in the item list on the customer's top screen (Fig. 65). In addition, the claim plan display process performs display of the claim plan. FIG. 54 is a flowchart showing the processing operation of the complaint plan display process.

  In S5401, a complaint proposal display page as shown in FIG. 70 is generated. In the claim proposal display page, in the left column, the case information (application number (= reception number), application number, name of invention, inventor name) acquired from the application file management table 6101 and the application case table 6001 using the reception number as a key. , Link to technical file). In the center of the page, the claim plan information obtained from the claim plan table using the receipt number as a key and the creator (patent attorney) who created it are displayed (if there are multiple patent attorneys who presented the claim plan) Will display multiple proposed claims).

  In the complaint proposal display page (FIG. 70), the customer looks at each complaint proposal, and if there is a favorite proposal, he / she requests the agent by pressing the “request button” (priority based on the emergency paper application). Request a proxy for a claim application. Also, if you select the link for the patent attorney's name, you can view the agent's evaluation information, which can be used as a reference when making a request. In addition, the claim proposal can be evaluated.

  S5402 to S5406 following S5401 are a loop waiting for an operation from the customer for the complaint proposal display page.

  In the input waiting loop of S5402 to S5406, if the “request button” is selected, a confirmation screen asking whether or not to really make the request is displayed (S5402 → S5407). The claim request flag in the table 6001 is set to 2, the patent attorney ID is registered in the corresponding record in the application file management table 6101, and the end flag is set to 1 (S5408 → S5409). In the subsequent S5410, a record using the receipt number as a key is generated in the billing table 6201, the procedure code is set to 3, the date of the day of the procedure is stored, and the ID of the patent attorney as the request destination is stored as the billing destination (ie In this embodiment, when a request is made, this is a business model in which a patent attorney who accepts a proxy is billed), and the settlement flag is 0. On the other hand, if cancel is selected on the confirmation screen (S5408), the process returns to S5401 and continues processing.

  In the input waiting loop of S5402 to S5406, when the link of the part of the patent attorney name is selected, an evaluation screen related to the patent attorney is displayed in a separate window (S5403 → S5411). As shown in FIG. 76, an example of an evaluation screen related to a patent attorney is displayed in the same way as the graph in FIG. 72, and a comment on a record obtained by searching the evaluation table 6301 using the patent attorney ID as a key is reviewed. It is displayed as information.

  In the input waiting loop of S5402 to S5406, when the link of the public document is selected, the corresponding document is displayed in another window based on the document address of the application item table 6001 (or the download screen is presented) (S5404 → S5412).

  When the “evaluation button” is selected in the input waiting loop of S5402 to S5406, a complaint evaluation page as shown in FIG. 71 is generated (S5406 → S5413). The claim evaluation page is the same as the evaluation page of FIG. 72, but only the evaluation of the claim proposal (and the description of comments) can be performed. If the send button is selected after the evaluation is input to the claim evaluation page, the process proceeds to S5415, and the acquired information is stored in the evaluation table 6301 (FIG. 63) with the receipt number as a key. Record generation and registration (if there is a record with the corresponding receipt number, update processing of the record). After the process of registering information in the evaluation table 6301 (S5415) or when the return button is selected on the complaint evaluation page (FIG. 71) (S5414), the process returns to S5401 and the process is continued.

  In the input waiting loop of S5402 to S5406 (for the complaint proposal display page (FIG. 70)), when the “return button” is selected, the complaint proposal display processing is terminated.

  Returning to FIG. 49 (customer response site processing), the description will be continued.

  After the complaint plan display process (S4915) ends, the process returns to S4901 to continue the process (returns to the top page of FIG. 65). If the end button is selected in the operation waiting loop of S4902 to S4905 for the page (S4905), the customer-facing site process is terminated.

  Through the above-described customer-facing site processing, the customer is requested to apply for an emergency paper (and amend it), the request for the drafting of a claim to the patent attorney, the presentation of the proposed draft of the claim, the draft of the claim and the proxy It is possible to provide various services such as human evaluation, proxy request referring to word-of-mouth information, input of evaluation information for a draft proposal, and description of various evaluations when a proxy is requested.

  Next, the use of this system from the patent attorney will be explained.

<< Office-Related Site Processing: Details of Processing at S4806 in FIG. 48 >>
When there is a login request from the patent attorney, the office corresponding site process is executed (FIG. 48: S4804 → S4806). FIG. 55 is a flowchart showing the processing operation of the office corresponding site processing.

  First, in S5501, processing for generating a site screen for a patent attorney as illustrated in FIG. 73 is executed. The top page of the patent attorney site displays a list of complaint request cases that are suitable for the logged-in patent attorney. “Applicable” is a case in which the technical fields are compatible, and the technical fields that can be handled by each patent attorney are registered in the patent attorney table 5903 in advance as technical field codes. Generate a list of complaint requests on the top page ("Requester", "Scheduled filing date", "Application date", "Application number", "Document link information", "Technical field", "Keyword", " As for “acquisition of whether or not a complaint plan has been created”, first, a case where the claim request flag is 1 is extracted from the application case table 6001 (FIG. 60), and the technical field code of the case is the corresponding patent attorney. Extract the case that matches the registered technical field code of (logged in patent attorney), and use the receipt number as a key for the extracted case, from the application case table 6001 to the applicant, desired application date, document address, Each information of the technical field and the keyword is acquired, the application date and the application number are acquired from the application file management table 6101 in the same manner, and its own I This is done by acquiring information on whether there is (logged patent attorney's ID) or not (if the complaint plan table 6401 has a record in which the ID is associated with the corresponding receipt number, Since the draft claim has been created, “completed” is displayed in the “created” item, and “not yet” is displayed if there is no corresponding record). In addition, in the case where the claim request flag is 2, if the self ID is stored as the patent attorney item in the application file management table 6101, the case is also added to the list and the note “Request ant” is noted. Add writing. This is a case where a customer requested a proxy for a case for which a draft proposal was created. (In this embodiment, after the proxy request, this system is not involved in this example. Recognized patent attorneys will contact the client individually and accept the work). For each item in the list, a create button or a modify button is assigned. In this assignment, a creation button is assigned to a case where the creation item is “not yet”, and a correction button is assigned to a case where the item is “completed”. Although not displayed on the screen, the reference number information of each item is held in association with each other for use in later processing.

  After the top screen display processing (S5501) of the patent attorney site, S5502 to S5507 are in a loop waiting for the occurrence of an event (operation on the top screen), and processing corresponding to the operation of the login user Will be executed.

  In the loop of waiting for operation on the top screen of S5502 to S5507, when the link of the material (technical information file) in the request list is selected, the material address acquired from the application matter table 6001 using the reception number as a key Based on this, the corresponding material is displayed in a separate window (or presentation of a download screen) (S5505 → S5509). As a result, the patent attorney can refer to the document that is the basis for preparing the draft claim, and inputs the draft plan created based on the document by the following processing.

  When the “Create button” is selected on the top screen (FIG. 73), a complaint proposal input screen as shown in FIG. 74 is generated (S5503 → S5510). In the claim proposal input screen, in the left column, "requester (institution requesting creation of claim proposal) information", "application number", "invention name", and "inventor" information are stored using the reference number as a key. Are obtained from each table and displayed. As an example of the input part of the main complaint plan, there are input fields for “challenge complaint”, “target complaint”, “estimated estimate”, and “comment”. In other words, by creating both a “challenge claim” that aims to acquire rights in a wide range within a certain meaning, and a “target claim” that aims to acquire rights in real terms, the agent's ability to create claims is improved. It is intended to be able to guess. Further, since the cost is also an important factor from the side requesting work, an approximate estimate (in this embodiment, the format is free) is presented. In the last comment field, an auxiliary explanation for allowing the customer to better understand the contents, such as the intention of making a claim, can be freely described.

  When a patent attorney inputs a complaint plan or the like on the complaint plan input screen and the confirmation button for the input content is pressed, a confirmation screen is displayed (S5511 → S5512). If the registration button is selected, the process proceeds to S5514 (on the other hand, if the return button is selected, the process returns to S5510 to repeat the process (S5513)). In S5514, a new record is generated and registered in the complaint plan table 6401 (FIG. 64) using the receipt number as a key for information such as the complaint plan input by the patent attorney. When the processing of S5514 is completed, or when a cancel button is input on the complaint proposal input screen (FIG. 74) (S5511), the processing returns to S5501 and is repeated.

  If a correction button is selected in the loop waiting for operation on the top screen in steps S5502 to S5507, a complaint plan correction screen is generated (S5502 → S5515). The structure of the claim plan correction screen is the same as that of the claim plan input screen of FIG. 74, and is displayed in a form in which already registered contents are entered. That is, each information of the record of the corresponding reception number and patent attorney ID is acquired from the complaint plan table 6401, and each column of “challenge complaint”, “target complaint”, “estimated estimated amount”, and “comment” in FIG. It is the screen which displayed each information on.

  When the patent attorney inputs correction information as appropriate to the complaint plan correction screen and the input content confirmation button is pressed, a confirmation screen as shown in FIG. 75 is displayed (S5516 → S5517). If the correction registration button is selected for the confirmation screen, the process proceeds to S5520 (on the other hand, if the return button is selected, the process returns to S5515 and repeats the process (S5518)). In S5520, the information such as the corrected claim plan is reflected in the claim plan table 6401 (FIG. 64). When the process of S5520 is completed, or when a cancel button is input on the complaint plan correction screen (S5516), the process returns to S5501 and is repeated. On the other hand, when the cancel button is selected on the confirmation screen (FIG. 75), the record is deleted from the complaint plan table 6401 using the receipt number and the patent attorney ID as keys (S5519 → S5521).

  In the loop waiting for operation on the top screen in steps S5502 to S5507, when “view evaluation” in the left column is selected, a personal evaluation screen as shown in FIG. 76 is generated (S5504 → S5508). As described above, the screen is generated by information obtained from the evaluation table 6301 using the patent attorney ID as a key. This makes it possible to know what the client's evaluation of self is.

  When “Registration information” in the left column is selected in the loop waiting for operation on the top screen in S5502 to S5507, a registration information display change screen as shown in FIG. 77 is generated (S5506 → S5522). This processing is to confirm and correct the information registered to receive the service by this system, and obtain the information of the corresponding patent attorney ID from the patent attorney table 5903 (FIG. 59 (c)). This is displayed, and when correction and confirmation are input for this, the correction information is reflected on the patent attorney table 5903.

  If “end” in the left column is selected on the top screen (FIG. 73), the office corresponding site processing is ended (S5507).

  Through the above-mentioned office-facing site processing, a complaint draft preparation request from a customer is presented, and the complaint draft is transmitted to the customer side by inputting the complaint draft created based on the material. It is also possible to know the customer's self-assessment and proxy request information.

<< Same-day application processing: details of processing in S4807 of FIG. 48 >>
In the loop processing of S4801 to S4803 in FIG. 48, when the time has reached midnight, “current day application processing” is executed (S4802 → S4807). “On-the-day case application processing” executes application processing of a case (thesis emergency application) on the scheduled application date. FIG. 56 is a flowchart showing the processing operation of this processing.

  The day application processing (FIG. 56) is to execute the processing of S5601 to S5605 for all the records of the application item table 6001 (FIG. 60). In S5601, it is determined whether or not the application desired date is today. In subsequent S5602, it is determined whether or not the end flag is 1. For cases where the desired application date is today and the end flag is not 1, the processing of S5603 to S5605 is executed, and for the cases that are not, the processing of S5603 to S5605 is skipped and the process proceeds to the next case (record) To do.

  In S5603, the application software is automatically started by the system, the application file address and the link file address are acquired from the application file management table 6101 based on the reference number of the corresponding case, and the files corresponding to these file addresses are used. Then, the application software executes application processing (conversion to transmission file and online application processing).

  In subsequent S5604, application information (application number, application date) obtained after the application processing is acquired, the information is recorded in a corresponding record of the application file management table 6101 (FIG. 61), and the application completion flag is set to 1. In addition, the application software outputs a receipt and a proof file (HTML converted file output), stores it in the DB, and records the address information of the file in the application file management table 6101 (in FIG. 61, the receipt is received). And the address information item of the proof file is omitted).

  In S5605, a record with the receipt number as a key is generated in the accounting table 6201 (FIG. 62 (a)), the procedure type code is set to 1, the application date on the procedure date, and the application number in the billing destination with the receipt number as a key. 0 is recorded in the applicant ID and settlement flag acquired from 6001.

  When the processing of S5601 to S5605 is executed for all the records in the application matter table 6001, the case application processing on the day ends. By this processing, the system automatically performs the application processing of the case for which the application desired date has arrived, and the registration and receipt of the application information and the acquisition of the proof file (HTML converted file).

<< Cancel Processing: Details of Processing of S4808 in FIG. 48 >>
In the loop processing of S4801 to S4803 in FIG. 48, if the time is 11:00 pm, “withdrawal processing” is executed (S4803 → S4808). The “withdrawal process” executes a withdrawal process for a case (paper urgent application) that is scheduled to be withdrawn. FIG. 57 is a flowchart showing the processing operation of this processing.

  The withdrawal process (FIG. 57) causes the processes of S5701 to S5706 to be executed for all records in the application item table 6001 (FIG. 60). In S5701, it is determined whether or not the desired withdrawal date is today, and in subsequent S5702, it is determined whether or not the end flag is 1. For cases where the desired withdrawal date is today and the end flag is not 1, the processing of S5703 to S5706 is executed, and for those cases that are not, the processing of S5703 to S5706 is skipped and the process proceeds to the next case (record) To do.

  In S5703, a withdrawal document is automatically generated. Since this process is the same as that of the first embodiment (the processes of S1503 to S1505 in FIG. 15), description thereof is omitted here. In subsequent S5704, the application software is automatically activated by the system, and the application software executes the withdrawal process (conversion to a transmission file and online processing) using the withdrawal document file generated in S5703.

  In subsequent S5705, the withdrawal date information is recorded in the corresponding record of the application file management table 6101 (FIG. 61), and the withdrawal flag and the end flag are set to 1. In addition, the application software outputs a receipt and a proof file (HTML converted file output), stores it in the DB, and records the address information of the file in the application file management table 6101 (in FIG. 61, the receipt is received). And the address information item of the proof file is omitted).

  In S5706, a record using the receipt number as a key is generated in the billing table 6201 (FIG. 62A), the procedure type code is set to 2, and the procedure date and the billing destination are obtained from the application case table 6001 using the receipt number as a key. 0 is recorded in the applicant ID and settlement flag.

  When the processing of S5701 to S5706 is executed for all records in the application matter table 6001, the withdrawal processing is terminated. By this processing, the system automatically performs the procedure for the case whose withdrawal date has arrived and the acquisition of a receipt and a proof file (HTML converted file).

<< Procedure Notification End Process: Details of Process of S4809 in FIG. 48 >>
Subsequent to the withdrawal process (S4808), a procedure end notification process is executed (S4809). “Procedure completion notification process” is a process of notifying the customer of the procedure performed on the day using this system. FIG. 58 is a flowchart showing the processing operation of this processing.

  The procedure end notification process (FIG. 58) causes the processes of S5801 to S5805 to be executed for all records in the accounting table 6201 (FIG. 62 (a)), and based on the information in the temporary table obtained thereby, This is for sending an email to the office (S5806). In step S5801, it is determined whether or not the procedure date is today. In subsequent step S5802, it is determined whether or not the settlement flag is 1 (that is, whether or not the payment has already been made). For cases where the procedure date is today and the settlement flag is not 1, the processing of S5803 to S5805 is executed, and for the cases that are not, the processing of S5803 to S5805 is skipped and the process proceeds to the next case (record). .

  In S5803, information is collected from each table, and for each billing destination, the receipt number, the procedure performed, the procedure date, and the billing amount are associated and temporarily stored. In this processing, the billing destination information is acquired from the customer table 5901 based on the billing customer ID of the billing table 6201 or from the patent attorney table 5903 based on the billing attorney ID of the billing table 6201. Is obtained from the office table 5902 based on this. A temporary table in this processing is generated for each customer ID or office ID obtained here (if a table with the corresponding ID already exists, it is used), and the reception number and the procedure performed (charging table 6201) are stored in the table. Procedure table 6202 (obtained with reference to FIG. 62B)), procedure date, billing amount (procedure table 6202 based on procedure type code of charging table 6201 (FIG. 62B)) ) Is stored in association with each other.

  In step S5804, it is determined whether or not the procedure type code is 1 or 2 (procedure using application software). If the procedure type code is a procedure using application software, the receipt and the application file management table 6101 are referred to. The storage location information of the proof file is acquired and stored in the temporary table (S5805).

  When the processing of S5801 to S5805 is executed for all records in the accounting table 6201, the loop processing is terminated, and the process proceeds to S5806. In step S5806, the procedure performed on the day for each billing destination is notified collectively using the temporary table obtained by the loop processing. That is, for each billing destination, generate an email with the receipt number, the procedure performed, the date of the procedure, and the billing amount (calculated and displayed for the total amount) (Attach this if there is a report and proof file) ) And send. When the process of sending e-mails to all billing destinations is completed, the procedure end notification process is terminated.

  After the procedure end notification process (FIG. 48: S4809) ends, the process proceeds to S4810 to execute the billing process. The billing process is a process of using the temporary table in the procedure end notification process to withdraw the total amount charged for each billing destination from each billing destination account (account information is obtained from the customer table 5901 or the office table 5902). I do. For those for which the withdrawal process has been completed, the settlement flag in the charging table 6201 is set to 1. In the present embodiment, an example is given in which the amount of procedure performed on the day is notified and charged every day, but the unit period for notification and charging may be arbitrary (for example, processing for each month) Or may be processed every time the procedure is performed).

  As described above, according to the application support system of the present embodiment, it is possible to provide each customer with a service on behalf of an emergency paper application based on a technical information file. Also, the technical information file etc. obtained from the customer is presented to the agent side, the input of the complaint proposal according to the contents of the technical information file etc. is accepted, and the obtained complaint proposal is sent to the customer (transmission of the technical information file) Since the processing to be presented to (main) is performed by the system, the customer who receives the provision of this service can check the draft complaint created by the agent based on the contents of the technical information file. In general, it is not possible to request a job after looking at a draft claim in an application request for an application. However, according to the service provided by this system, it is possible for customers to check and compare each draft proposal and request work by referring to the evaluation information and word-of-mouth information of each agent. Useful services can be provided.

  In addition, for the complaint draft created by the agent based on the contents of the technical information file, the evaluation information is stored in association with the agent, in response to a request from the customer or a request from the agent, Since the evaluation information is presented, it is possible to provide a service that presents information that evaluates the claim creation ability after viewing an actual claim plan. Further, since the evaluation other than the claim creation ability can be evaluated only at least for the agent who actually requested the job, a service for presenting useful information can be provided.

  In this embodiment, since the service is based on an individual patent attorney rather than on an office basis, information such as who the creator of the claim proposal is and evaluation information for the individual can be obtained. The ability to create patent specifications depends largely on the individual ability rather than the office unit, and there is a demand for a good patent attorney (or patent engineer) to request work from the office. It is difficult to find a patent attorney (or patent engineer) who can be an individual unit rather than a unit unless he is a mentor. On the other hand, according to this system, the evaluation information by the person who actually requested the work is stored and provided in individual units, and the person who created it when presenting the draft claim is By presenting whether there is, the convenience of customers such as universities who are requesting work is enhanced.

  With the service provided by the system of this embodiment, the agent can also get an opportunity to acquire a new customer. It becomes easy to reach a virtuous cycle of increasing. As a result, the function of improving the quality of service of the overall agent can be expected.

  In this embodiment, the technical information file such as a paper is used as the material to be presented to the agent when requesting the creation of a draft draft. However, it may be an HTML file for application automatically generated by the system, or the application software after application. May be a proof file obtained from the above (as is clear from the above description, both contents are the same).

  In this embodiment, the customer side is an example of a patent attorney when confirming a draft claim, or a customer who can only see evaluation information related to the corresponding patent attorney when inputting an evaluation. You may search and display evaluation information. For example, a process in which a technical field is specified and persons with high evaluation information in the field are sequentially displayed, or a process in which search is performed by direct patent attorney name and the evaluation information is presented may be performed. The same service may also be provided to the patent attorney.

  In the present embodiment, it is basically described that the “emergency application for paper” in the first embodiment is performed, but the applicant (the person who intends to apply) simply does not submit the emergency application for the paper. And a system that mediates between the agent side. In other words, the agent side looks at the application material (technical information file) registered in the system by the applicant side, creates a draft claim and registers in the system, and the applicant side refers to these draft claims etc. (Also, as can be understood from the above description, the word-of-mouth information for each agent can also be used as a reference), and provides a service that can decide which agent to ask. .

  In addition, although the description of the preparation of the application specification has been described here, it can be applied to the intermediate processing in the patent business, and more generally, it is a concept applicable to other agency services. (Uploading the materials necessary for the request → presenting the agent's action plan based on the materials → selecting the agent by the client side can be applied as a similar concept). In other words, the technical information file from the applicant in the above embodiment is considered as request information from the client, and the draft draft created by the agent in the above embodiment is considered as correspondence information for the request information. Therefore, it can be used as a more general agent evaluation / referral service support system. One embodiment of the agent evaluation / introduction service support system will be described in the third embodiment below.

(Embodiment 3)
The agent matching support system according to the third embodiment provides a service as a system for matching an agent and a client. By using this system, a client (side using an agency service) can provide a service. This makes it possible to select the most preferable agent by comparing the actual ability of a plurality of agents and so-called word-of-mouth information. Hereinafter, the agent matching support system of Embodiment 3 will be specifically described with reference to the drawings. In each drawing, the same reference numerals as those of the respective embodiments are used for the same components and processing concepts as those of the first or second embodiment, and the description thereof is omitted or simplified.

  FIG. 78 is a block diagram showing an outline of an agent matching support system according to the third embodiment. As shown in the figure, a contractor system 780, a client PC 479 which is an information processing apparatus used by the client, an agent PC 478 which is an information processing apparatus used by the agent, and the like are constituent elements. The supplier system 780 includes an agent matching support server 781 (agent evaluation / introduction service support server), a requester DB 782, an agent DB 783, a request / evaluation DB 784, and the like. The agent matching support server 781 is not particularly different from that of the first and second embodiments as hardware, but there is a difference in function from the first and second embodiments, and will be described below. In order to realize the function, each program, table, and the like different from those in the first and second embodiments are provided. Each function processing unit (login processing unit, request information acquiring unit, request information presenting unit, corresponding information acquiring unit, corresponding information presenting unit, corresponding condition information acquiring unit, agent designation by each hardware resource such as CPU and each program An information acquisition unit, an agent evaluation information acquisition / presentation unit, a request input unit, a request reception / notification processing unit, and a billing processing unit) are the same as those in the first and second embodiments.

  In this embodiment, both the requester and the agent are registered in advance as the service provision target, and the requester table 8401 (the configuration example shown in FIG. (Stored in the requester DB 782), in addition to the ID and password as login information, the name / name, address, whether it is a corporation or an individual, the name of a person in charge of a corporation, and contact information (phone number) Etc.), information such as e-mail address, type of business, job type, and years of experience is acquired in advance at the time of registration and stored in association with each other. Note that information stored in the table (for example, information such as whether it is a corporation or an individual, type of industry, occupation, and years of experience) is the attribute information of the requester. In the present embodiment, the attribute information is not essential information for registration, but is information that is arbitrarily input by the client during registration. The attribute information shown here is an example, and is not limited to these, and is appropriately determined according to the characteristics of each agency.

  As for the agent side, in the agent table 8402 (stored in the agent DB 783) as shown in FIG. 84B, in addition to the ID and password as login information, the name, e-mail address, telephone number, Information such as a FAX number, information on fields that can be supported, information on fields that cannot be handled, clients that cannot be handled, and years of experience are acquired in advance during registration, and these are stored in association with each other. Note that information on compatible fields, information on fields that cannot be handled, information about clients that cannot be handled, information such as years of experience, etc. is the condition information or / and the information that cannot be handled. This information is not necessarily essential information for registration, but is information that a proxy inputs arbitrarily at the time of registration.

<Overall processing of proxy matching support server>
An overview of the entire processing operation in the agent matching support server 781 of this embodiment will be described, and thereafter, each functional process constituting the entire process will be described in detail sequentially. FIG. 79 is a flowchart showing an outline of the overall operation of the agent matching support server 781.

  The outline of the overall operation of the agent matching support server 781 is basically the same as that in the second embodiment (FIG. 48) (some functions are not processed), and when there is a login (S4801: Yes), Depending on whether the logged-in person is a client or an agent, a corresponding process is executed (S4804 → S4805orS4806).

<< Requester Response Site Processing: Details of Processing in S4805 of FIG. 79 >>
When there is a log-in request from the requester, the requester corresponding site process is executed (FIG. 79: S4804 → S4805). FIG. 80 is a flowchart showing the processing operation of the requester corresponding site processing.

  First, in S8001, the requested case table 8501 (FIG. 85) is referred to, and based on the ID of the logged-in requester, whether there is a case requested by the requester (the corresponding requester ID is Whether or not there is a record associated therewith).

If there is a requested matter as a result of the determination processing in S8001, the process proceeds to S8002 to execute processing for generating a site screen for the client as illustrated in FIG. The top page of the client site presents a list of cases that have been requested by the logged-in client. For the generation of the list (acquisition of “reception number”, “request date”, “title”, “request content” in the list), the requester ID (= login ID) from the request item table 8501 (FIG. 85). This is done by acquiring necessary information from the record extracted based on.
Regarding the remarks column, when there is a record of the corresponding receipt number in the request correspondence plan table 8701 (FIG. 87), a message “There is a comment” is displayed (information is given to the delegated agent in the request matter table 8501 (FIG. 85)). If there is, the display will indicate “Agent requested”). In addition, the display of the remarks column is not necessarily displayed exclusively, and when it corresponds to both, it is displayed by listing.

  After the top screen display process (S8002), S8003 to S8005 are a loop for waiting for the occurrence of an event (requester's operation on the top screen), and processing corresponding to this is executed according to the requester's operation. Will be.

  “Request input” in the left column of the top screen (FIG. 88) is for accepting a new request, and when the item is selected, accepting processing is executed (S8003 → S8006). Also, as a result of the determination processing in S8001, even when there is no requested matter, the reception processing is executed (S8001 → S8006).

<<< Reception Processing: Details of Processing in S8006 in FIG. 80 >>>
FIG. 81 is a flowchart showing the processing operation of the reception process in this embodiment, and corresponds to the process of S8006 of FIG. The same reference numerals are used for the same processing concept as the reception process of the first embodiment (FIG. 6) or the reception process of the second embodiment (FIG. 50), and the description thereof is omitted here.

  In step S8101, a new request page generation process as shown in FIG. 89 is performed. This page requests input of a request title, request content, information on the field of the request, information on an agent that transmits the request content, and the like. Note that “information about the agent who transmits the request content” corresponds to the corresponding condition information. With this setting, it is possible to specify a partner (agent) to disclose the request contents. In this embodiment, as shown in FIG. 89, a radio button for an item “restrict to those who fit the field” and a button for transitioning to a screen for selecting an agent in more detail are arranged. . When “restrict to those who fit the field” is selected, the contents of the request are presented only to the agent who fits the field selected on that.

  In the loop processing of S8102 to S8103 after the generation process of the new request page, it waits for selection of each button (“select agent in detail”, “confirm input contents”, “cancel”) for the new request page. On the other hand, if “select agent in detail” is selected, the process proceeds to S8104 to generate an agent selection page as shown in FIG. 90 and select the agent. Process.

This process is performed when an agent that meets the search condition is selected when the “search agent” button is selected in the state where various search conditions are specified on the agent selection page of FIG. The extracted agent is extracted from the table 8402, and the extracted agent is displayed as a list, and the requester selects it (for example, selecting all of the list or selecting an arbitrary person. In this case, the agent is evaluated. It is a process of acquiring a proxy (which may be used as a reference for selection by making it possible to see information) (the ID (single or plural) of the proxy acquired thereby is displayed in the request matter table 8501, Registered as a designated agent).
More specifically, for example, when a field is specified on the agent selection page of FIG. 90, agents whose names are registered as compatible fields are extracted in the agent table 8402. If limited to those with a track record is selected, the requested matter table 8501 is referred to, and the field information of the case in which the ID is registered as the delegate agent and the agent to which the designated field matches are specified. Extracted (or excluded). When the evaluation is selected, an agent (based on the information in the evaluation table 8601) having evaluation information suitable for it is extracted. For example, when a specific company name or the like is input with respect to the “agent who has a proxy record of the next person”, the requester ID of the item whose ID is registered as a delegated agent with reference to the request item table 8501 In the case of matching with the name obtained based on the above, the agent is extracted (when “specify” is selected) or excluded (when “exclude” is selected). This processing realizes the function when, for example, it is not desired to show the request information to a person acting for a specific company. With respect to keywords, for an input of an arbitrary keyword, an agent that matches the keyword is determined based on information in each table. Of course, a plurality of the above conditions can be set.

  Through the above process, an agent is selected, and the agent ID (s) acquired thereby is registered as a designated agent in the request item table 8501 (FIG. 85) (note that the registration process to the actual table) Is executed in S5002 instead of S8104), the request information is disclosed only to the agent (that is, the agent that meets the conditions specified by the client, or the agent who is directly appointed Request information is disclosed only to In addition, it is possible not to make any setting for “information about the agent sending the request contents”. In that case, the request information is basically disclosed to all registered agents. (However, this does not apply to cases where the agent has set “impossible companies” or “impossible fields” and the request falls under this category).

  The screen of FIG. 89 is waited for selection of the “confirm input contents” button or the “cancel” button (S8103). After these buttons are selected, basically the first embodiment (FIG. 6) or The processing concept is the same as that of the second embodiment (FIG. 50).

  Returning to FIG. 80 (requester response site processing), the description will be continued.

  When the comment display is selected in the waiting for input to the top screen (Fig. 88) (S8003 to S8005) (when "There is a comment" in the remarks column of the project list is clicked), the comment display process is performed. Execute (S8004 → S8007).

<<< Comment Display Processing: Details of Processing in S8007 in FIG. 80 >>>
The contents of the matter requested by the requester are presented by the system to the agent that meets the specified conditions (the agent whose ID is registered in the specified agent in the request item table 8501 by the above-mentioned processing). Comments from the agent side (advice on request contents, suggestion of solution, suggestion of response policy, estimate information when actually accepted) are input to the system (the processing concept is Embodiment 2). the same as). When a comment is registered from the agent, the corresponding item in the item list on the top screen (Fig. 88) is displayed as "There is a comment". The comment display process performs the display and the like. FIG. 82 is a flowchart showing the processing operation of the comment display processing.

  In S8201, a comment display page as shown in FIG. 91 is generated. In the comment display page, in the left column, the title and request contents text acquired from the request matter table 8501 using the receipt number as a key are displayed, and in the center of the page, the receipt number is keyed from the request correspondence plan table 8701 (FIG. 87). The comment or estimated amount acquired in the above and the agent who created the comment are displayed (if there are a plurality of agents who presented the comment, a plurality of comments will be displayed).

  On the comment display page (FIG. 91), the requester sees each comment, and if there is a favorite plan, the request can be made to the agent by pressing the “request button”. When the link of the name of the agent is selected, the evaluation information of the agent can be viewed, and this can be referred to when making a request. In addition, comments can be evaluated.

  Each processing subsequent to S8201 is basically the same processing concept as that of the second embodiment (FIG. 54). However, when there is an actual request (S5402 → S5407 → S5408), the requested item in S8202 The ID of the agent who made the request is registered as an authorized agent of the corresponding record in the table 8501 (extracted using the receipt number as a key). In subsequent S8203, a charging process is executed. In the system according to the present embodiment, when delegation is actually established on the system (that is, when matching between the client and the agent is performed by the system), the system charges the agent side. Therefore, in S8203, a charging process for the agent is performed (the charging process itself can be performed by various known methods).

Further, in the screen for inputting the evaluation of the comment of the agent (S5406 → S5413), in the present embodiment, the input evaluation information is reflected as a display (display when displaying the evaluation information of the agent). Timing can be set (acquisition of reflection condition information).
For example, it is intended not to be reflected as a display until the number of evaluations reaches a predetermined number, and the requester (evaluator) is allowed to set the predetermined number of cases (others such as setting a predetermined period) May be).

When the input of the evaluation for the comment is completed and received (S5414), the evaluation information obtained thereby, the reflection condition information, ID (both agent and evaluator (requester)), etc. are used as the reception number. The data are stored in the evaluation table 8601 (FIG. 86) in association with each other (S8204).
By this process, the requester ID is associated with the evaluation information, and therefore the attribute information of the requester is also associated. Thereby, in the evaluation information display processing (for example, S5411 in FIG. 82), the evaluation information display processing that has been subjected to the aggregation processing according to the attribute information of the requester can be performed. For example, if this system is a system for matching patent attorneys and clients as in the second embodiment, the attributes of the clients (for example, whether they are individuals or corporate employees, intellectual property, What kind of evaluation do you receive from individuals based on information such as whether you are a legal person or a development person? What is the evaluation from development staff? It is possible to see evaluation information from various viewpoints. In addition, although the specific example about an evaluation item and an evaluation screen is not shown here, these are suitably determined, such as reflecting the characteristic in each agency business.

  Further, in S8204, processing for storing points assigned at a predetermined rate (appropriately set) in accordance with the amount of registration information of the evaluator (requester) in the requester table 8401 (FIG. 84) is executed. . “Amount of registered information” is the amount of information (attribute information) registered in the requester table 8401 (FIG. 84). As described above, in order to display evaluations from various viewpoints, it is necessary to register the requester's attribute information. However, since the registration of the information is indispensable for some operations, the client basically registers the information arbitrarily, and it may be difficult to register without any incentive. Therefore, more points are given to the person who performed the evaluation after registering more attribute information so as to be the incentive. Although the specific use of the points is not described in the present embodiment, the point use method may be determined as appropriate (for example, when a request is actually made to an agent, a request is made. The points can be used as rewards paid by the agent to the agent).

  Returning to FIG. 80 (requester response site processing), the description will be continued.

  After the comment display process (S8007) ends, the process returns to S8002 to continue the process (return to the top page of FIG. 88). If the end button is selected in the operation waiting loop of S8003 to S8005 for the page (S8005), the requester corresponding site process is terminated.

  Through the above-mentioned client-facing site processing, the client receives the request, presents a comment from the agent, evaluates the request, evaluates the agent, evaluates the actual request based on the word-of-mouth information, and evaluates the comment. Various services such as information input can be provided.

  Next, the use of this system from the agent side will be described.

<< Site-Responding Site Processing: Details of Processing of S4806 in FIG. 79 >>
When there is a login request from the agent, the agent corresponding site process is executed (FIG. 79: S4804 → S4806). FIG. 83 is a flowchart showing the processing operation of the agent corresponding site processing.

In S8301, processing for generating a site screen for the agent as illustrated in FIG. 92 is executed. The top page of the agent site displays a request item that matches the logged-in agent.
“Applicable” means that it conforms to the disclosure conditions set by the client as described above. Specifically, as the designated agent in the request item table 8501 (FIG. 85), the self ID is Registered cases are extracted. In addition, when the agent has registered information such as areas that cannot be handled or companies that cannot be handled, the information is not displayed even if it meets the disclosure conditions set by the client. Specifically, as a designated agent of the requested matter table 8501, for a matter whose own ID is registered, the field and requester information acquired from the requested matter table 8501 are represented in the agent table 8401 (FIG. 84). When dealing with information on unacceptable fields or unacceptable companies, the matter is not subject to display. In this case, a case where the agent knows that the case cannot be accepted due to a conflict or the like is excluded from the display target. In addition, although the impossible field | area and the impossible company are mentioned here as an example, it is not restricted to this, It determines suitably according to the characteristic of each agency business, etc.

  Necessary information is acquired from the request item table 8501 (FIG. 85) for the item extracted by the above processing concept, and a site screen for the agent as illustrated in FIG. 92 is generated and displayed. In addition, referring to the request correspondence plan table 8701 using the reception number and the self agent ID as a key, if there is a corresponding record, the “Create” column in FIG. 92 is set to “Done” and there is no record. In this case, the creation button is assigned after “not yet”. Whether or not there is a request is determined and displayed depending on whether or not there is a self ID as an acceptance agent of the record of the corresponding reception number in the request matter table 8501 (FIG. 85).

  After the agent site screen display process (S8301) in FIG. 92, the processing concept is basically the same as that in the second embodiment (FIG. 55), and thus the description thereof is omitted here. In the evaluation display process in S5508, as described above, various display processes according to the attributes of the client are possible. If a reflection condition is set in the evaluation table 8601 (FIG. 86), the evaluation is totaled / displayed according to the condition. For example, when it is set not to be displayed until the evaluation exceeds 10, the number of existing records is extracted from the evaluation table 8601 using the agent ID as a key, and there are no 10 records. Is to exclude the evaluation information from the evaluation aggregation / display processing target. As a result, the evaluation information is presented to the agent at the timing desired by the evaluator (requester). If a predetermined period is set as a reflection condition, the request date is acquired from the request matter table 8501 and the evaluation information is subject to evaluation aggregation / display processing until the predetermined period elapses from the request date. It is processing to be excluded from.

As described above, according to the agent matching support system of the present embodiment, the request information obtained from the requester is presented to the agent side, and the corresponding information according to the content of the request information (advice and solution for the request content) The system performs a process of accepting input of a suggestion of a law, a suggestion of a response policy, etc., and presenting the obtained response information to the client. Thereby, the client who receives the provision of the service can confirm the correspondence information created by the agent based on the contents of the request information.
In addition, the agent ID and corresponding condition information (for example, various information such as own specialized field information, industry type, delivery date, amount, etc.) and / or unacceptable information (similarly, field information, industry type, delivery date, The amount of money and various names such as specific company names that cannot be handled are stored in association with each other, and at the time of request, the corresponding condition information (same field information, industry type, delivery date, amount of money, specific company name, etc.) Since the request information is presented to a suitable agent based on these information, an efficient service can be provided. In addition, since the request information is unnecessarily presented, it is excellent from the viewpoint of confidentiality.
Also, evaluation information for the correspondence information created by the agent based on the content of the request information is stored in association with the agent, and the evaluation information is stored in response to a request from the client or a request from the agent. Since it is presented, it is possible to provide a service that presents information that evaluates its ability after seeing actual correspondence information (that is, quality of service provided by the agent).
Since the evaluation information and the attribute information of the requester are stored in association with each other, it is possible to display according to the attribute information of the requester (= evaluator) when presenting the evaluation information. is there.
In addition, until the predetermined number of evaluation information or until a predetermined period elapses, the evaluation information is not targeted for presentation, so it will be immediately noticed that the evaluation agent has entered the evaluation information. Is deterred.
It becomes possible to associate more specific service information (for example, points, cashback information, etc.) with a client who has entered evaluation information after registering more attribute information. In other words, in order to increase the value of this system, it is indispensable to enrich the evaluation information (= improve the value as a DB), so we offer a service that gives more preferential treatment to clients who have enriched the information. By providing, it gives incentives to actions that lead to DB value enhancement.

  In each of the above-described embodiments, information (technical information file and request information) transmitted from the requester side is highly confidential information. Therefore, when transmitting / receiving the information, SSL or the like is encrypted. It is desirable to use a protocol for transmitting information. In the system related to the present invention, since it is assumed that a qualified person logs in except for the client, it is assumed that only those who have confidentiality obligations will access, but who You may make it memorize | store the agent ID which accessed the technical information file and request information so that the requester side can confirm whether it accessed. Furthermore, a confidentiality agreement may be concluded when accessing a technical information file or request information. For the conclusion of the confidentiality agreement, an electronic signature may be used to ensure that the parties have contracted electronically (using the electronic signature, the system Specifically, for example, the system presents the text of a standard confidentiality agreement (you may automatically insert the names of the client and agent) If the agent approves this, the agent will give it an electronic signature and return it (and keep it on the system side).

  111 Application file creation support server, 112 Application HTMLLD (external storage device), 113 Administrator PC (administrator terminal device), 114 Application file DB (external storage device), 121 Researcher PC (inventor terminal device), 11111 CPU (control unit, calculation unit), 11112 memory (storage unit), 11113 communication unit, 1112 storage device (storage unit), 471 file creation support server for application, 472 customer file DB, 478 Patent office PC (agent) Terminal device), 479 Customer PC (customer terminal device)

Claims (33)

An application support system comprising an application file creation support server, an administrator terminal device, an inventor terminal device, and a network,
The application file creation support server is connected to the manager terminal device and the inventor terminal device via the network so that they can communicate with each other,
The application file creation support server includes:
A technical information file acquisition unit for acquiring a technical information file and inventor information from the inventor terminal device via the network;
An application generation unit that automatically generates an application using the acquired inventor information and preset applicant information;
A specification automatic generation unit that automatically generates a specification by converting the acquired technical information file into an image file for each page and pasting each image file to each automatically generated paragraph number;
An application file that automatically generates a predetermined format application file in a format accepted by the electronic application software using the generated application and specification, and stores the predetermined format application file in a storage area accessible by the administrator terminal device A generator,
An application support system comprising:   An application file creation support server that supports creation of application documents for patent applications or utility model registration applications, a control unit that controls the entire apparatus, a storage unit, a communication unit, a file imaging unit, A technical information file acquisition unit for acquiring the technical information file and the inventor information via the network by the communication unit and storing the technical information file and the inventor information in association with each other, and an application using the inventor information A specification generation unit that automatically generates a specification by converting the technical information file into an image file by the file imaging unit and pasting the image file on a paragraph number; An application file generation unit that automatically generates a predetermined format application file in a format accepted by the electronic application software using the generated application and specification; File storage processing for sending the information from the communication unit to store the predetermined format application file in the storage area of the storage unit or to store the predetermined format application file in the storage area of a preset external device And an application file creation support server.   The file imaging unit acquires print output data using a print function of application software corresponding to the technical information file, and executes conversion from the print output data to the image file. Item 3. An application file creation support server according to Item 2.   Obtaining the technical information file and the inventor information via the site by providing a technical information file receiving site presenting section for presenting a site for accepting transmission of the technical information file and the inventor information from the file holder 4. The application file creation support server according to claim 2, wherein the application file creation support server is provided. In the acquisition process of the technical information file and the inventor information by the technical information file acquisition unit, the scheduled application date information or the scheduled release date information of the technical information file is also acquired, and in the storage process by the file storage processing unit, the application A daily folder storage processing unit for storing the predetermined format application file in a daily folder corresponding to a date and time derived directly or indirectly from the scheduled date information or the scheduled date information;
Alternatively, in the storage process of the predetermined format application file in the storage area, the application scheduled date information or the publication scheduled date information is stored in association with each other, and provided with a date and time function unit, the application scheduled date information or the A file transfer processing unit on the day for moving the predetermined format application file to a predetermined folder when there is the predetermined format application file whose date and time derived directly or indirectly from the scheduled release date information corresponds to the current day; The file creation support server for application according to any one of claims 2 to 4, characterized in that:   An application number generation unit that automatically generates reference number information including information indicating that the application is automatically generated by the application file creation support server, and a date / time function unit, and the application generation by the application generation unit The application is automatically generated using the reference number in the process, and the date obtained by the date / time function unit has reached the date / time derived directly or indirectly from the scheduled application date information or the scheduled release date information, or When the time has elapsed, obtain the reference number information of the predetermined format application file corresponding to the date and time derived directly or indirectly from the scheduled application date information or the expected release date information, based on the reference number information, Search the folder where the accepted file obtained by the application process of the electronic application software is stored, and accept the accepted file corresponding to the reference number. If there is no application date information or application number information corresponding to the reference number by searching the list output file output from the electronic application software, the administrator information set in advance 6. The application file creation support server according to claim 5, further comprising an accepted file confirmation unit that transmits warning information to an administrator based on the file.   By providing an employee discriminating unit that discriminates whether or not the inventor is an employee based on the inventor information, and an administrator site presenting unit that presents an administrator site that receives information from the administrator, When it is determined by the employee discriminating section that an inventor who is not an employee is included, information on the corresponding technical information file and the inventor information are displayed on the administrator site, 7. The application file creation support server according to claim 2, wherein execution of the automatic generation processing of the predetermined format application file is permitted when the approval information is input. .   Compare the date / time function unit with the date obtained by the date / time function unit and the date / time derived directly or indirectly from the scheduled application date information or the scheduled release date information, and whether this is shorter than a preset period The application file creation support according to claim 5, further comprising: a grace period determination unit that determines whether or not the predetermined format application file is automatically generated when it is short. server.   If the technical information file reception site presenting section presents a site for requesting whether or not the technical information file is required to be in color, and if the technical information file is essential in color, If the technical information file is not a PDF file, convert it to a PDF file instead of the automatic generation process for the statement, and convert it to a PDF file. The application file creation support server according to any one of claims 2 to 8, wherein a process of pasting the file is executed.   The technical information file receiving site presenting section obtains keyword information via the site by causing the technical information file receiving site presenting section to present a site for requesting keyword information related to the technical information file, and associates the keyword information with the technical information file. The file creation support server for application according to any one of claims 4 to 9, wherein the file is stored in the storage unit or a storage area of a preset external device.   The date / time function unit, the date obtained by the date / time function unit, and the application date are compared, and it is determined whether or not this exceeds a preset period. A period elapse confirmation unit that transmits predetermined period elapse information to an administrator based on the information, and an application withdrawal form generation unit that automatically generates an application withdrawal form for an application for which the predetermined period has elapsed. The file creation support server for application according to any one of claims 5 to 10.   Acquire a technical information file and inventor information via the network by the communication unit to an information processing device including a control unit, a calculation unit, a storage unit, and a communication unit that controls the entire device And storing the application in the storage unit or the external storage device, and using the inventor information and a template file set in the storage unit or the external storage device in advance, the application unit automatically generates the application unit. A step of converting the technical information file into an image file by the calculation unit; and a step of automatically generating a specification unit by pasting the image file to a paragraph number by the calculation unit with respect to the template file And the automatically generated file is stored in a predetermined file format that is a predetermined file format.憶領 region or preset external device application for file creation support program steps to be stored in the storage area, characterized in that for the execution to the.   In the step of converting the technical information file into an image file for each page, print output data is obtained by executing a printing function of application software corresponding to the technical information file, and conversion from the print output data to the image file is performed. 13. The application file creation support program according to claim 12, wherein a process for executing is executed.   In the acquisition process of the technical information file and the inventor information, a step of acquiring the scheduled application date information or the scheduled release date information of the technical information file, and directly or indirectly from the scheduled application date information or the planned release date information 14. The application file creation support program according to claim 12 or 13, further comprising: storing the predetermined format application file in a daily folder corresponding to the derived date and time.   In the acquisition process of the technical information file and the inventor information, the step of acquiring the scheduled application date information or the scheduled release date information of the technical information file, and the storage process of the predetermined format application file in the storage area The predetermined format application file in which the application date information or the publication date information is stored in association with the application date and the date derived directly or indirectly from the application date information or the publication date information. 14. The application according to claim 12 or 13, characterized in that a step of determining whether or not a file exists and a step of moving the predetermined format application file to a predetermined folder when the file exists are executed. File creation support program.   In the acquisition process of the technical information file and the inventor information, acquiring the application scheduled date information or the scheduled release date information of the technical information file, and storing them in the storage unit or the external storage device in association with each other; When the date and time derived directly or indirectly from the scheduled application date information or the scheduled publication date information is reached, the automatic generation process of the predetermined format application file is executed, and the predetermined format application file is stored in the predetermined folder 14. The file creation support program for application according to claim 12 or 13, wherein the step is executed.   A step of automatically generating reference number information including information indicating that the application is automatically generated by the file creation support server for the application, and the application part using the reference number information in the automatic generation processing of the application part And when the date and time derived directly or indirectly from the scheduled application date information or the scheduled release date information is reached, the serial number information of the predetermined format application file corresponding to the date and time is acquired. Based on the step and the reference number information, if there is no accepted file corresponding to the reference number by searching the folder where the accepted file obtained by the application processing of the electronic application software is stored, or the electronic application Search the list output file that is output from the software, and the expected filing date information or application number information corresponding to the reference number is It claims 14 to application file creation support program according to claim 16, characterized in that to execute a step of outputting warning information when bought, the.   The step of determining whether or not the inventor is an employee based on the inventor information, and if it is determined by the determination process that the inventor is not an employee, The application file creation support program according to any one of claims 12 to 17, wherein the execution process of the automatic generation process of the predetermined format application file is not performed until the approval information is input.   Determining whether or not a period from the scheduled application date information or the scheduled release date information to a date or time derived directly or indirectly is longer than a preset reference period; and The file creation support program for an application according to any one of claims 14 to 16, wherein a step of not executing the automatic file generation processing is executed.   A step of obtaining information as to whether or not the technical information file needs to be in color or a step of automatically determining whether or not the technical information file is in color; and if the technical information file is in color In the automatic generation of the application, a template file in a foreign language document is used. If the technical information file is not a PDF file instead of the automatic generation process of the specification, it is converted into a PDF file. The application file creation support program according to any one of claims 12 to 19, wherein a step of pasting an item name "foreign language document" is pasted.   A step of determining whether or not the elapsed period from the filing date has reached a preset withdrawal notification period, and in this case, a step of outputting information notifying the withdrawal timing or a withdrawal notice period An application file creation support program according to any one of claims 14 to 16, wherein the program automatically generates an application withdrawal notice for an application. An application support system comprising an application file creation support server, a customer terminal device, an agent terminal device, and a network,
The file creation support server for application is connected to the customer terminal device and the agent terminal device so as to be communicable via the network,
The application file creation support server includes:
A login processing unit that performs a login process in response to a login request from the customer terminal device;
A technical information file acquisition unit for acquiring a technical information file and inventor information from the customer terminal device via the network;
A request generation unit that automatically generates a request using the acquired inventor information and the applicant information specified by login;
A specification automatic generation unit that automatically generates a specification by converting the acquired technical information file into an image file for each page and pasting each image file to each automatically generated paragraph number;
An application file generation unit that automatically generates a predetermined format application file in a format accepted by the electronic application software using the generated application and specification;
An application support system comprising:   An application file creation support server that supports the creation of application documents for patent applications or utility model registration applications, and stores a control unit that controls the entire apparatus, customer login information, and applicant information in association with each other. The storage unit, the communication unit, the file imaging unit, the login processing unit that performs the login process, and the communication unit acquires the technical information file and the inventor information via the network and associates them with each other. A technical information file acquisition unit to be stored in a storage unit or an external storage device, an application generation unit that automatically generates an application using the inventor information and applicant information specified by login, and the technical information file The file imaging unit converts each page into an image file and pastes each image file into each automatically generated paragraph number A specification automatic generation unit that automatically generates, and an application file generation unit that automatically generates a predetermined format application file in a format accepted by the electronic application software using the generated application and specification. Application file creation support server.   Agent log-in information is stored in the storage unit, and technical information that presents the technical information file, the predetermined format application file, or an application file acquired from the electronic software when there is a login from the agent To the customer who sent the technical information, etc. to the file proposal section, the complaint proposal acquisition section that asks the agent to input the corresponding complaint proposal and obtains the proposed complaint information. 24. The application file creation support server according to claim 23, further comprising a claim plan presentation unit that presents the claim plan.   When the complaint plan is presented to the customer, the storage unit is requested to input evaluation information for the complaint plan, and the evaluation information obtained thereby is associated with the ID of the agent who has input the complaint plan. 25. The application according to claim 24, further comprising an agent evaluation information acquisition / presentation unit that is stored in an external storage device and presents the evaluation information in response to a request from a customer or a request from an agent. File creation support server.   The agent evaluation information acquisition / presentation section asks the customer who requested the application to the agent to input the evaluation information about the agent who is the application request destination, and the evaluation information obtained thereby is The information processing apparatus further includes a process of storing the evaluation information in association with an agent ID and storing the information in the storage unit or the external storage device and presenting the evaluation information in response to a request from a customer or a request from an agent. 25. An application file creation support server according to 25.   When submitting a claim proposal to the customer, the application request input means for the agent who input the claim proposal is presented, and if there is an input to this, the agent has been requested to apply 25. An application request reception / notification processing unit for presenting an application request and a billing processing unit for performing billing processing for the agent when the application request information is provided. 26. An application file creation support server according to any one of 26.   A step of performing a login process in response to a login request from an external device to an information processing device including a control unit that performs overall control of the device, a calculation unit, a storage unit, and a communication unit; And acquiring the technical information file and the inventor information via the above and associating them with the log-in person information and storing them in the storage unit or the external storage device; A step of automatically generating an application part by the calculation unit using a set template file, a step of converting the technical information file into an image file for each page by the calculation unit, and for the template file A statement part is automatically generated by pasting each image file to each paragraph number automatically generated by the arithmetic part. Application file creation support program characterized by executing the flop, the.   29. The file creation for application according to claim 28, wherein the electronic application software is started by the arithmetic unit, and the electronic application software is caused to execute application processing of the predetermined format application file. Support program.   Proxy login information is stored in the storage unit, and when the login from the proxy is made, the technical information file or the application file obtained from the predetermined format application file or the electronic software is presented; , Requesting the agent to input the corresponding claim plan, obtaining the claim plan information obtained thereby, storing it in association with the agent information, and sending the technical information to the customer 30. A file creation support program for an application according to claim 28 or 29, wherein the step of presenting the draft of the claim is executed.   A step of requesting input of evaluation information for the complaint plan when the complaint plan is presented to the customer, and storing the evaluation information obtained thereby in association with the ID of the agent who has input the complaint plan 31. The application file creation support program according to claim 30, wherein the evaluation information is presented in response to a request from a customer or a request from an agent.   When submitting a claim proposal to the customer, the application request input means for the agent who input the claim proposal is presented, and if there is an input to this, the agent has been requested to apply 32. The file for application according to claim 30 or 31, wherein the step of presenting the application request and the step of charging the agent when the application request information is provided are executed. Creation support program.   Requesting the customer who made the application request to input evaluation information relating to the agent who is the application request destination, and storing the evaluation information obtained thereby in association with the ID of the agent; 33. The file creation support program for application according to claim 32, wherein the step of presenting the evaluation information is executed in response to a request from an agent or a request from an agent.