Information processing device, method, program

Abstract

Technologies are needed to further promote space development by making the request for services related to space development even smoother. [Solution] A program is provided for operating a computer equipped with one or more computer processors. In the memory unit, information of entities conducting space development and information of the entities' past achievements in space development are recorded in association with each other. The program causes one or more computer processors to perform the following steps: acquire information on the details of a request for work related to a space project; extract entities with experience corresponding to the request based on the acquired information on the details of the request and the information on the space development achievements of each entity stored in the memory unit; and present the extracted entities and the information on the space development achievements of the extracted entities to the user making the request.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, method, and program.

Background Art

[0002] Space development has been attracting attention, and the government, private companies, etc. are engaged in the development of space machines. In the space industry, project entities such as the government are advancing projects related to space development. On the other hand, space development by private companies is also expected, and as an industry, it is necessary to make it easier for various operators to participate. As a result, various requests for space development-related operations are carried out among various operators, and it is described that space development will be further promoted.

[0003] Patent Document 1 points out that in the field of "an online printing system that places an order, prints, and arranges delivery based on an order signal from an orderer's terminal via the Internet", "it is being considered to make a soft packaging material printed with a design specified by a user also a target of online ordering", and as a problem, "since the printable range varies depending on the shape of the soft packaging material, when acquiring print data from the orderer, it is necessary to receive data corresponding to the print range from the orderer", and a technique for dealing with this is described.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] On the other hand, space development has often progressed in the form of developing specialized spacecraft to achieve objectives such as exploration. As a result, the number of companies participating in space development has been limited, making it difficult to acquire the necessary expertise and hindering the participation of various companies in space development. Space development requires various tasks such as design, manufacturing, and processing, but it is difficult for a single company to handle all of these tasks, such as material development, processing, and control software development. For example, different companies may be responsible for developing materials for spacecraft, processing hardware, and manufacturing. Furthermore, spacecraft vary in size from large to small depending on their purpose, making it difficult to find companies that can undertake development tailored to new objectives. For example, in order to develop a small robot for exploration, a public tender may be held.

[0006] To promote space development, it is crucial to make it easier for companies responsible for development and operation to participate. In addition to this, there is a need for technologies that will further promote space development by making the request process for services related to space development even smoother. [Means for solving the problem]

[0007] According to one embodiment shown in this disclosure, a program is provided for operating a computer having one or more computer processors. In the memory unit, information of entities conducting space development and information of the entities' past performance in space development are recorded in association with each other. The program causes one or more computer processors to perform the following steps: acquire information on the details of a request for work related to a space project; extract entities that have experience corresponding to the request based on the acquired information on the details of the request and the information on the past performance of each entity stored in the memory unit; and present the extracted entities and the information on the past performance of the extracted entities to the user making the request. [Effects of the Invention]

[0008] According to this disclosure, requests for services related to space development can be made more smoothly, and space development can be further promoted. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows the configuration of System 1. [Figure 2] Figure 2 shows the configuration of server 20. [Figure 3] Figure 3 shows the configuration of terminal 10. [Figure 4] Figure 4 shows the data structure of the user database 211. [Figure 5] Figure 5 shows the data structure of the constraint database 212. [Figure 6] Figure 6 shows the data structure of the spacecraft sample database 213. [Figure 7] Figure 7 shows the data structure of the astronaut database 214. [Figure 8] Figure 8 shows the data structure of the Space Project Database 215. [Figure 9] Figure 9 shows the data structure of the design history database 216. [Figure 10] Figure 10 shows the data structure of the matching database 217. [Figure 11] Figure 11 shows the data structure of the Space Development Personnel Database 218. [Figure 12] Figure 12 shows the data structure of the development spacecraft database 219. [Figure 13] Figure 13 shows the data structure of the insurance application history database 220. [Figure 14] Figure 14 shows the data structure of the financial support history database 221. [Figure 15] Figure 15 shows the data structure of the rights transaction history database 222. [Figure 16]FIG. 16 is a diagram showing the flow of a process for performing a simulation according to the constraint conditions of the space environment based on design data. [Figure 17] FIG. 17 is a diagram showing the flow of a process for evaluating an operator engaged in space development. [Figure 18] FIG. 18 is an example of a screen for searching for operators related to a space development project. [Figure 19] FIG. 19 is an example of a screen for a simulation of controlling multiple spacecraft as a group while they are coordinated. [Figure 20] FIG. 20 is an example of a screen for performing a simulation to determine whether it is suitable in the space environment based on design data. [Figure 21] FIG. 21 is an example of a screen for presenting simulation results on a 3D model based on design data. [Figure 22] FIG. 22 is a diagram showing the flow of a process for calculating a score for evaluating a space project. [Figure 23] FIG. 23 is a diagram showing the flow of a process for accepting an application for insurance for a space project. [Figure 24] FIG. 24 is a diagram showing the flow of a process for accepting a transaction regarding financing for a space project. [Figure 25] FIG. 25 is a diagram showing the flow of a process for accepting a transaction regarding investment in a space project. [Figure 26] FIG. 26 is an example of a screen for accepting an application for insurance for a space project. [Figure 27] FIG. 27 is an example of a screen for accepting a transaction regarding financing for a space project. [Figure 28] FIG. 28 is an example of a screen for accepting a transaction regarding investment in a space project. [Figure 29] FIG. 29 is a diagram showing the data structure of the human resource matching database 223. [Figure 30] FIG. 30 is a diagram showing the data structure of the desired human resource database 224. [Figure 31]Figure 31 shows the process flow for calculating the score of space personnel. [Figure 32] Figure 32 shows the process flow for registering the career information of space personnel. [Figure 33] Figure 33 shows the process flow for accepting registrations of information on desired space personnel. [Figure 34] Figure 34 shows the process flow for matching job seekers and employers in the space industry. [Figure 35] Figure 35 shows an example of a screen that displays scores to space personnel while also accepting requests for job matching. [Figure 36] Figure 36 shows an example of a screen where employers can specify their desired space personnel. [Figure 37] Figure 37 shows an example of a screen display when a match is made between a job seeker and a company offering space-related services. [Figure 38] Figure 38 shows the data structure of the request details registration database 225. [Figure 39] Figure 39 shows the process flow for matching business requests by extracting potential service providers based on the requester's registration of the request details and accepting the requester's specifications. [Figure 40] Figure 40 shows the process flow for matching business requests by having the requester register the details of the request, and the entity receiving the request specifying the details of the request. [Figure 41] Figure 41 shows an example of a screen where a client registers the details of their request for services. [Figure 42] Figure 42 shows an example of an operation screen that allows the requester to specify candidate service providers extracted according to the content of the request. [Figure 43] Figure 43 shows an example of an operation screen that allows a requester to specify transaction terms to a party capable of fulfilling the request. [Figure 44]Figure 44 shows an example of a screen display where potential service providers search for requests registered by the client and apply to accept the request. [Modes for carrying out the invention]

[0010] Embodiments of this disclosure will be described below with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions of them will not be repeated. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each figure is a schematic diagram and is not necessarily a strict illustration.

[0011] Furthermore, in the following description, "processor" refers to one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core.

[0012] Furthermore, at least one processor may be a broad-sense processor, such as a hardware circuit that performs some or all of the processing (e.g., an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)).

[0013] Furthermore, in the following explanation, we may use expressions such as "xxx table" to describe information that yields an output for a given input. This information can be data with any structure, or it can be a learning model such as a neural network that generates an output for a given input. Therefore, "xxx table" can be referred to as "xxx information."

[0014] Furthermore, in the following explanation, the structure of each table is just an example; one table may be divided into two or more tables, or all or part of two or more tables may be a single table.

[0015] Furthermore, in the following explanation, the subject of the process may sometimes be "program," but since a program is executed by a processor and performs defined processes using the memory and / or interface as appropriate, the subject of the process may also be the processor (or a device such as a controller that has that processor).

[0016] The program may be installed on a device such as a computer, or it may reside on a program distribution server or a computer-readable (e.g., non-temporary) recording medium. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

[0017] Furthermore, in the following explanation, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including letters or symbols) may also be used.

[0018] Furthermore, in the following explanations, when describing similar elements without distinction, a reference code (or a common code among reference codes) may be used, and when describing similar elements with distinction, the element's identification number (or reference code) may be used.

[0019] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.

[0020] <Outline of Embodiment 1> <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.

[0021] System 1, shown in Figure 1, includes a server 20, user terminals 10 and 10A, a terminal 30 for the administrator of the space development project, a terminal 40 for the client of the space development project, an artificial intelligence (large-scale language model) service server 95 (hereinafter sometimes referred to as "large-scale language model service server 95"), a product manufacturer's server 96, and an advertising distribution service server 97. These devices communicate with each other via a network 80.

[0022] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, the collection of each device can be considered as a single "information processing device," and System 1 may be formed as a collection of multiple devices. The way in which the multiple functions required to realize System 1 according to this embodiment are distributed to one or more hardware can be appropriately determined in view of the processing capacity of each hardware and / or the specifications required for System 1.

[0023] Server 20 provides the following to the user in general terms: • A service that provides simulations according to the constraints of space development for companies developing spacecraft. • A service that matches companies that conduct space development with companies that provide financial support for space development, thereby promoting financial support for space projects. • A service that supports the careers of personnel involved in space development by matching them with companies that conduct space development and facilitating transfers between organizations through job changes, etc. • A service that supports transactions between those who request services related to space development and those who fulfill those requests. The following provides a detailed explanation.

[0024] Server 20 matches space development companies with companies that provide financial support for space development, thereby promoting financial assistance for space projects. Server 20 collects various information on space projects and calculates an evaluation value for each project. By providing these evaluation results to companies that provide financial support, it is possible to encourage loans or investments. Furthermore, based on these evaluation results, it can calculate insurance premiums for space projects and present these premiums to companies involved in space projects, accepting applications from them.

[0025] Server 20 may evaluate the space project by assessing the organizational structure required to carry it out, and evaluates the space project from the perspectives of (1) the development resources required for the space project, and (2) the operational resources required for the space project.

[0026] (1) As part of evaluating the development resources involved in the space project, for example, Server 20 evaluates development resources such as the performance of the spacecraft, the system for developing the spacecraft, and the track record of development in order to assess the likelihood that the space project can be evaluated as successful by achieving its initial objectives.

[0027] (2) As part of the evaluation of operational resources for space projects, Server 20 evaluates the resources needed to launch and operate spacecraft. For example, the following accuracy and track record may be evaluated as part of the evaluation of resources needed to operate spacecraft. • By launching spacecraft, monitoring their orbits, and predicting their trajectories, collisions with other spacecraft such as satellites can be prevented during launch. • Monitoring whether satellites and other spacecraft in orbit are still in orbit. This can be done by monitoring devices on the ground, or by satellites in space sensing other spacecraft. • Controlling the attitude of a spacecraft. For example, to improve the efficiency of generating energy for the spacecraft's operation using solar power, the attitude of the spacecraft may be controlled so that its solar panels are at an optimal angle to the sun. Also, to enable communication with other spacecraft, the attitude of the spacecraft may be controlled so that its antenna is pointed in the appropriate direction. • Controlling the attitude of a spacecraft and controlling thrusters to accelerate or decelerate it. To control such thrusters, a model is prepared that predicts the spacecraft's inertia and its flight path based on thruster control. For example, in order to dock spacecraft with a space station, spacecraft may need to be brought into space at a predetermined position and angle. • Monitoring space objects such as debris and predicting their orbits. For example, if there is a risk of debris colliding with a spacecraft such as a satellite, it may be possible to remove the debris or change the orbit of the spacecraft at risk of collision. As described above, Server 20 can evaluate the likelihood of a space project achieving its intended objectives and other successes by assessing the development and operational resources involved in the space project.

[0028] Here, the server 20 may determine the evaluation value as follows in order to assess the probability of success. • The position of the team involved in a project within the overall picture. For example, whether their development and operational track record is among the top tier (a certain percentage from the top). For example, by aggregating the number of projects they were involved in and the budget size of each project for each company, it is possible to determine the ranking of their development track record. • Whether or not it meets the standards set by the government or other relevant bodies. For example, whether or not the quality of the software code meets certain standards. • The likelihood of success for the current space project compared to past successful or unsuccessful space projects. For example, if the performance of the spacecraft in this project is significantly improved compared to past successful space projects, or if operational experience has been accumulated, the project may be evaluated as having a higher probability of success than past projects. Server 20 provides a service for simulating the space environment. For example, Server 20 receives data related to the design of a ground-based vehicle from the user's terminal 10, determines whether it conforms to constraints such as gravity, temperature, communication, power, air, and radiation in space development, and provides the simulation service by responding with the determination result to the user's terminal 10. Server 20 can also provide the service by having Server 95, an artificial intelligence (large-scale language model) service, generate the content of the response to the user, and then responding with the generated result to the user.

[0029] Server 20 provides a service to device developers that performs simulations according to the constraints of space development. For example, it constructs the environment inside a spacecraft (ISS: International Space Station, space colony), the environment outside the spacecraft, the environment in orbit, the lunar surface environment such as terrain and day / night cycle, and the surface environment of planets such as Mars in a virtual space, and performs simulations of controlling spacecraft objects placed in that virtual space.

[0030] Server 20 provides services to support career changes and other transitions for personnel involved in space development. For example, Server 20 evaluates personnel involved in space development based on their track record of participating in space projects. In this evaluation, Server 20 assesses the compensation (e.g., annual salary) that should be paid for the work performed by personnel involved in space development. Server 20 accepts registration of job information from recruiting companies and matches it with job seekers. Server 20 also presents recruiting companies with the expected compensation for the personnel they are recruiting. This enables the transfer of personnel between organizations.

[0031] Server 20 accepts user registrations and project registrations from clients and administrators of space development projects. Through this, Server 20 provides services to match space development projects with device development companies, including searching for device development companies and searching for space development projects.

[0032] Server 20 is connected to Server 96, which represents product manufacturers that provide ready-made products, and accepts product registrations from manufacturers of components, finished products, etc. This allows Server 20 to provide a search function for ready-made products to stakeholders in space development projects and businesses developing devices.

[0033] Server 20 is connected to Server 97 of the advertising distribution service, and delivers advertisements to various users of Server 20, such as device developers, based on their usage history of the services provided by Server 20. For example, based on the history of a device developer designing a spacecraft using Server 20's simulation service, advertisements can be delivered that are tailored to the purpose of the spacecraft and the components that make up the spacecraft, thereby promoting matching with products offered by advertisers.

[0034] Terminal 10 is the terminal of a user who uses the services provided by Server 20. In the illustrated example, terminals 10, terminal 10A, etc., are shown as terminals used by users of the services provided by Server 20, but each user operates their own terminal. For example, a user of a space project development company, a user of an investment company, and a user of a lending company each operate Terminal 10.

[0035] Server 95 of the Large-Scale Language Model Service is a server that executes language processing tasks using language models built through learning processes including artificial intelligence (AI). An LLM (Large Language Model) is a model that has been pre-trained on large amounts of data (such as text data), for example, a large amount of web content on the internet, or a large amount of data stored in a designated database, and can perform various language processing tasks by being given a task.

[0036] The server 95 of the large-scale language model service accepts prompt input in the form of text, images, audio, etc., and generates and responds with answers to those prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0037] The configuration of each device is described below.

[0038] The server 20 includes a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29.

[0039] Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0040] Input / Output IF23 functions as an interface between an input device for receiving user input operations and an output device for presenting information to the user.

[0041] Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0042] Storage 26 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0043] The processor 29 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0044] Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PCs (Personal Computers), Laptop PCs • Wearable devices worn by the user (watch-type, glasses-type, etc.) Terminal 10 includes a communication interface (IF) 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19.

[0045] The communication interface 12 is an interface for inputting and outputting signals so that terminal 10 can communicate with an external device.

[0046] The input device 13 is a device for receiving input operations from the user (for example, a touch panel, touchpad, pointing device such as a mouse, keyboard, etc.).

[0047] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0048] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0049] Storage 16 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0050] The processor 19 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0051] <1.2 Functional Configuration of Server 20> Figure 2 shows the configuration of server 20. As shown in Figure 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0052] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

[0053] The memory unit 202 stores various databases, including a user database 211, a constraints database 212, a spacecraft sample database 213, an astronaut database 214, a space project database 215, a design history database 216, a matching database 217, a space development personnel database 218, a developed spacecraft database 219, an insurance application history database 220, a financial support history database 221, a rights transaction history database 222, a personnel matching database 223, a desired personnel database 224, and a request content registration database 225.

[0054] User Database 211 is a database that manages information on each user involved in the development of spacecraft. Further details will be provided later.

[0055] The constraint database 212 is a database that holds constraints in space development. Further details will be provided later.

[0056] Spacecraft Sample Database 213 is a database of sample design data for spacecraft that meet the constraints of space development. Further details will be provided later.

[0057] Astronaut Database 214 is a database of astronauts. Further details will be provided later.

[0058] Space Project Database 215 is a database of space development projects. Further details will be provided later.

[0059] The design history database 216 is a database that manages the history of spacecraft designs created by users through a service provided by server 20. Further details will be described later.

[0060] The matching database 217 is a database that manages the history of matches made by users or businesses using the matching function provided by server 20. Further details will be described later.

[0061] The Space Development Personnel Database 218 is a database containing information on the achievements of personnel involved in space development. Further details will be provided later.

[0062] The Development Spacecraft Database 219 is a database of spacecraft developed by development companies. Further details will be provided later.

[0063] Insurance application history database 220 is a database that manages the history of insurance applications made for space projects. Further details will be provided later.

[0064] The Financial Support History Database 221 is a database that manages the history of loans or investments provided to space projects. Further details will be provided later.

[0065] The Rights Transaction History Database 222 is a database that manages transactions of rights that grant benefits for investing in space projects. Further details will be provided later.

[0066] The Talent Matching Database 223 is a database that manages the matching of personnel involved in space development with companies that are recruiting. Further details will be provided later.

[0067] The Desired Talent Database 224 is a database in which employers who are recruiting manage information on the types of candidates they wish to hire. Further details will be provided later.

[0068] The Request Details Registration Database 225 is a database that manages requests for services related to space projects and the transactions associated with those requests. Further details will be provided later.

[0069] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs the functions shown as the reception control module 2041, transmission control module 2042, user management module 2043, project registration module 2044, simulation processing module 2045, matching processing module 2046, score calculation module 2047, transaction acceptance module 2048, personnel evaluation module 2049, personnel matching module 2050, and business request matching module 2051.

[0070] The receive control module 2041 controls the process by which the server 20 receives signals from external devices according to a communication protocol.

[0071] The transmission control module 2042 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.

[0072] The user management module 2043 is a module for managing information for each user using System 1. Specifically, the user management module 2043 accepts registration of each user's information and updates the user database 211.

[0073] Project registration module 2044 accepts registrations for space development projects and updates the space project database 215 based on the input of project implementation status. It is a program module.

[0074] Simulation processing module 2045 is a program module that provides spacecraft developers with the functionality to simulate the space environment.

[0075] The simulation processing module 2045 provides users with space environment simulation capabilities in the following manner: • Constructs a three-dimensional virtual space that reflects the conditions inside and outside the ISS, and on the lunar or planetary surface (gravity, atmosphere, etc.), and returns simulation results of controlling a spacecraft (in-space drone, satellite, lunar rover, etc.). The system accepts registration of device design data from the user and determines whether the device meets the constraints based on information about constraints such as gravity, as shown in the constraint database 212. For example, upon receiving registration of design data for a ground-based device, if it does not meet the communication constraints in space development, the system determines that it cannot be used in the space environment (will not operate as intended) and presents the determination result to the user. Here, design data may be information from the device specifications, or information such as device design drawings or 3D models. Matching processing module 2046 is a program module that performs the process of matching each user (or each business).

[0076] The matching processing module 2046 accepts operations to search for each user (or each business), returns search results according to each user's (or each business's) score, and accepts operations to contact each user via message, etc., thereby promoting transactions for each user.

[0077] The score calculation module 2047 is a program module that evaluates space projects and calculates a score for them.

[0078] The score calculation module 2047 calculates a score that assesses the likelihood of a space project succeeding.

[0079] Transaction Acceptance Module 2048 is a program module that accepts applications for insurance, loans, and investments related to space projects and updates various databases.

[0080] The transaction acceptance module 2048 accepts insurance applications from space project operators and updates the insurance application history database 220; accepts loan or investment applications for space projects and updates the financial support history database 221; and accepts transactions for rights to receive benefits such as profit sharing for space projects and updates the rights transaction history database 222.

[0081] The Human Resources Evaluation Module 2049 is a program module that calculates scores for evaluating personnel based on information accumulated in various databases about personnel involved in space projects, and updates these databases accordingly.

[0082] The personnel evaluation module 2049 evaluates personnel involved in spacecraft development and the operation of space development projects based on various databases, such as the space project database 215, the design history database 216, the space development personnel database 218, and the developed spacecraft database 219, and updates the user database 211.

[0083] The Talent Matching Module 2050 is a program module that manages the history of matching between personnel involved in space development and companies that are recruiting.

[0084] The talent matching module 2050 receives registrations of desired personnel information from recruiting companies and updates the desired personnel database 224. The talent matching module 2050 also receives operations from personnel involved in space development, such as accepting job offers or expressing a desire to change jobs, and updates the talent matching database 223 to match them with recruiting companies.

[0085] The task request matching module 2051 is a program module that manages task requests related to space projects and updates the task request registration database 225.

[0086] More specifically, the business request matching module 2051 is a program module that handles tasks such as receiving business requests from clients and managing the recipients of those requests.

[0087] <1.3 Configuration of Terminal 10> Figure 3 shows the configuration of terminal 10.

[0088] As shown in Figure 3, terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units corresponding to each antenna (first communication unit 120, second communication unit 121), an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a storage unit 180, and a control unit 190. Terminal 10 also has functions and configurations not specifically shown in Figure 3 (for example, a battery for maintaining power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in terminal 10 is electrically connected by a bus or the like.

[0089] Antenna 111 radiates signals emitted by terminal 10 as radio waves. Antenna 111 also receives radio waves from space and provides the received signals to first communication unit 120.

[0090] Antenna 112 radiates signals emitted by terminal 10 as radio waves. Antenna 112 also receives radio waves from space and provides the received signals to the second communication unit 121.

[0091] The first communication unit 120 performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 111 in order to communicate with other wireless devices. The second communication unit 121 also performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 112 in order to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are a communication module that includes a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first communication unit 120 and the second communication unit 121 perform modulation and demodulation, frequency conversion, etc., of the wireless signals transmitted and received by the terminal 10, and provide the received signal to the control unit 190.

[0092] The input device 130 has a mechanism for receiving user input operations. Specifically, the input device 130 is configured as a touchscreen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives user input operations of the terminal 10. The touch-sensitive device 131 detects the user's contact position with the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's contact position detected by the touch panel to the control unit 190 as an input operation.

[0093] The display 132 displays data such as images, videos, and text in accordance with the control of the control unit 190. The display 132 is implemented by, for example, an LCD or an organic EL display.

[0094] The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal received from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is implemented, for example, by an audio processing processor. The microphone 141 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 140. The speaker 142 converts the audio signal received from the audio processing unit 140 into sound and outputs the sound to the outside of the terminal 10.

[0095] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal 10, which is equipped with a GPS module, is detected based on the received signals.

[0096] Camera 160 is a device that receives light using a photodetector and outputs it as an image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the object being photographed.

[0097] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10.

[0098] The storage unit 180 is composed of, for example, flash memory and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0099] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the memory unit 180 and executing the instructions contained in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 performs the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a memory control unit 195.

[0100] The operation reception unit 191 processes input operations from the user to an input device such as a touch-sensitive device 131. Based on the coordinate information of the touch-sensitive device 131 where the user's finger or the like has made contact, the operation reception unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation.

[0101] The transmitting / receiving unit 192 performs processing to enable the terminal 10 to send and receive data with an external device such as a server 20 in accordance with a communication protocol.

[0102] The data processing unit 193 performs calculations on the data received as input by the terminal 10 according to the program and outputs the calculation results to memory or other locations.

[0103] The notification control unit 194 performs the following processes: displaying the display image on the display 132, outputting sound to the speaker 142, and generating vibrations.

[0104] The memory control unit 195 controls the storage of data to the memory unit 180.

[0105] The various types of information stored by the memory unit 180 will now be explained. In a given scenario, the memory unit 180 stores various types of information, such as user information 181 and ground machine design information 182.

[0106] User information 181 is information about a user who uses the services of server 20.

[0107] Ground equipment design information 182 is information about the design data of the ground equipment. For example, if the user is a company that develops, maintains, and operates ground equipment, it will have design data such as specifications, design drawings, and test data for that ground equipment.

[0108] <2 Data Structure> Figure 4 shows the data structure of the user database 211. The user database 211 includes the fields "User ID", "Name", "Email Address", "Business ID", "Profile", "Attributes", and "Evaluation Score".

[0109] The "User ID" field is information that identifies each user.

[0110] The "Name" field contains information indicating the user's name.

[0111] The "Email Address" field contains the user's email address information, which is used as their contact information.

[0112] Specifically, the item "email address" contains email address information, which serves as user identification information for accepting user logins to the services provided by server 20.

[0113] The "Business ID" field is information that identifies the organization to which the user belongs.

[0114] Specifically, the "Business ID" field is information that identifies the organization to which the user belongs, and the following types of organizations are possible: • Businesses that design, develop, manufacture, process, and transport devices, software, etc., related to space development. • Client for space development projects • An administrator who manages the progress of a space development project based on a commission from the project's client. • Businesses that provide financial support to space development projects through loans or investments. The "Profile" item contains information about the user's profile.

[0115] Specifically, the "Profile" field stores the following information as profile information entered by the user: • Technologies with a proven track record • Specialized fields • Career history including previous employers • Areas in which we have a track record of providing loans. • Areas in which we have a track record of investment The "Attributes" field contains information about the attribute tags assigned to the user.

[0116] Specifically, the "Attributes" field allows users to be associated with tags corresponding to their roles in the project, enabling these tags to be used for user searches and other purposes. • Tags for device developers (tags indicating that technology development is being conducted) • Project Manager Tag • Tags of project clients • Material procuring tag Additionally, tags may be assigned according to the role of providing financial support to the project. • Loan officer tag • Investment Manager Tag The "Evaluation Score" item contains information about the evaluation value associated with the user.

[0117] Specifically, the item "Evaluation Score" may retain information on the score calculated as follows as an evaluation value for the user designing the device. In addition to being a user evaluation, it may also be retained as an evaluation value for the business to which the user belongs. For example, the business's evaluation value may be determined based on the evaluation values ​​of users belonging to the business (averaging, weighting, etc.), or the evaluation of a user may be treated as the evaluation value of the business to which the user belongs. • History of device design using the simulation service provided by server 20 (see, for example, design history database 216) • A history of when devices designed using the simulation service provided by server 20 have been viewed by other users, and a history of when they have been adopted in projects (see, for example, design history database 216). • In the matching function provided by Server 20, the history of searches by other users and the history of successful matches (transactions that have started) are recorded. • History of spacecraft development (see, for example, Development Spacecraft Database 219) • Track record of personnel belonging to the company participating in space projects (see, for example, Space Development Personnel Database 218) The "Reward Score" item is information about the evaluation results that assess the rewards that should be awarded to the user.

[0118] Specifically, the item "Reward Score" may hold the following evaluation result information. • Multiple evaluation levels based on reward ranges (e.g., classified into levels A, B, ..., etc.) The "Annual Income Equivalent" item is information about the evaluation results, which assess the compensation that should be given to the user based on their annual income.

[0119] Specifically, the "Annual Salary Equivalent" item may store information on the evaluation result expressed as an annual salary in a currency corresponding to the country where the job-seeking user is located, such as US dollars or Japanese yen, or the country where the employer is located.

[0120] The item "Reward Score Disclosure Status" is information that reflects the user's preference regarding whether or not to disclose the evaluation items "Reward Score" or "Annual Income Equivalent" for the user.

[0121] Specifically, the item "Disclosure of Compensation Score" may include information indicating whether or not the job seeker has specified whether or not to disclose the information for the items "Compensation Score" and "Annual Salary Equivalent" to the employers making the job.

[0122] The item "Reward Score Evaluation Reason" contains information on the reasons for the evaluation results shown in the items "Reward Score" and "Annual Income Equivalent".

[0123] Specifically, the item "Reward Score Evaluation Reason" may include the following information: • Compensation was evaluated based on the position (standard score) of development and operational performance within the overall workforce (for example, those with relatively strong performance and a high ranking). • Compensation was evaluated by comparing it to the salary levels of organizations with a certain level of experience in space development. • Having worked for a specific company (such as a company with a certain level of experience in space development), and the period of that employment was evaluated. The item "Aptitude Tests and References" contains information on the results of aptitude tests for a given employee, as well as information on evaluations (references) from other employees.

[0124] Specifically, the item "Aptitude Test / Reference" may include the following information: • Aptitude test: Information that determines suitable tasks and workplaces based on an individual's abilities, personality, and character. • Reference: Information from evaluations by other candidates. If the candidate is recommended by the other candidate, they may be considered to have met the aptitude test requirements. The item "SNS Account" contains information about social media accounts.

[0125] Specifically, the item "SNS account" may include the following information: • Influence on social media (number of followers, number of post impressions, etc.). The extent of a person's public relations activities can be evaluated based on such influence indicators, and this can be used to assess the expected value of talent acquisition, fundraising, and partnerships with businesses. Figure 5 shows the data structure of the constraint database 212. The constraint database 212 includes the fields "Constraint ID", "Major Category", "Medium Category", "Minor Category", and "Constraint".

[0126] The item "Constraint ID" is information that identifies each constraint in space development.

[0127] The "Major Category" item indicates the broad category of the constraints.

[0128] Specifically, the "Major Category" item includes information on constraints for the following categories. There may be stricter performance constraints than for ground-based spacecraft (e.g., communication speed constraints). Also, the devices that can be adopted and the performance requirements may differ depending on the mission to be achieved with the spacecraft. Furthermore, conditions may differ depending on the space environment, such as inside the ISS, outside the ISS, or on the lunar surface. For example, the requirements for the environment inside the ISS include requirements for volume, power, communication, heat dissipation, gas disposal, and gas supply. Similarly, the requirements for the environment outside the ISS include requirements for power, communication, heat dissipation, and vibration environment. • Gravity constraint: The gravity is extremely small compared to that on Earth. For example, gravity inside and outside the ISS is on the order of 10 to the power of minus 6 compared to Earth, and on the lunar surface it is on the order of one-sixth, so the control of device movement may differ from that of ground-based vehicles. • Temperature constraint: Temperature changes can be significant compared to ground level. For example, while the temperature inside the ISS is assumed to be around 18 to 27 degrees Celsius, outside the ISS, it can be around -150 degrees Celsius in the shade and +120 degrees Celsius in sunlight. On the lunar surface, it can be around -170 degrees Celsius at night and +110 degrees Celsius during the day. The requirements for devices to withstand temperature changes that are not anticipated for ground-based devices may differ from those for ground-based devices. Furthermore, outside the ISS, heat from direct light, reflected light, infrared radiation, and cosmic microwave background radiation must be considered. The dew point inside the ISS is set to be approximately 4°C to 16°C. Communication constraints For example, the bands, communication capacity, and communication ports that can be used by spacecraft are defined and may differ from those of ground-based spacecraft. The communication environment may also be slower compared to ground-based spacecraft. • Power constraints For example, the total power consumption of a spacecraft may be determined according to the specific spacecraft. • Atmospheric constraints: Space approaches a vacuum.

[0129] For example, the atmospheric pressure inside the ISS is approximately 98-103 kPa, similar to that on Earth, while outside the ISS it is 10⁻⁵ Pa, and on the lunar surface it is zero Pa (extreme vacuum). The partial pressure of oxygen inside the ISS is sometimes set to approximately 20-23 kPa. The partial pressure of carbon dioxide inside the ISS may be kept below 707 Pa. The relative humidity inside the ISS is sometimes set to 25-70% RH. The circulating air velocity inside the ISS is sometimes set to approximately 0.07 to 0.2 m / s. • Constraints on radiation: There may be constraints such as plasma, ionizing radiation, and electromagnetic waves.

[0130] For example, regarding plasma, outside the ISS, the electron density is on the order of 10¹² electrons / cubic meter on the sunlit side. This can cause static charge, discharge, surface damage to materials, and malfunction of equipment. For example, ionizing radiation can cause malfunctions outside the ISS. For example, electromagnetic waves outside the ISS could potentially cause deterioration of parts and materials, and discoloration of paints and other materials. The "Subcategory" item indicates a category within a medium-level framework that is further subdivided within the broader category of constraints.

[0131] The "Subcategory" item provides information indicating more detailed categories that are further subdivided within the medium-level constraint framework.

[0132] Specifically, the "subcategory" item may be divided into categories such as "inside the ISS" and "outside the ISS," as shown in the diagram.

[0133] The item "Constraints" is information that indicates the constraints that are determined based on the factors that affect devices in space development.

[0134] Specifically, the item "Constraints" may hold the parameters that constitute constraints in each environment as described above.

[0135] Figure 6 shows the data structure of the spacecraft sample database 213. The spacecraft sample database 213 includes the following items: "Sample ID", "Attributes", "Sample Data", "Usage Conditions", "Sample Provider", "Number of Uses", and "Used Project".

[0136] The "Sample ID" field is information that identifies each piece of sample data for the spacecraft.

[0137] The "Attributes" field contains information indicating the attributes of the spacecraft.

[0138] Specifically, the "Attributes" field contains information that identifies the attributes of each of the following spacecraft. • Spaceship ·satellite • Devices such as drones that operate inside the ship • Experimental equipment and other devices that operate outside of a ship • Devices such as rovers for exploring the lunar surface, etc. • Components that make up each of these devices The item "Sample Data" contains sample design data for a device designed with the constraints of the space environment in mind.

[0139] Specifically, the "Sample Data" item, as shown in the diagram, stores sample data associated with the attributes of the spacecraft, making it easy to search for sample data based on those attributes.

[0140] The "Terms of Use" section contains information about the conditions for using the sample data, as determined by the business or other entity that provided the sample data.

[0141] Specifically, the item "Terms of Use" includes information on the following conditions: • Usage fees: Usage fees may vary depending on the purpose of use, as follows. • Purpose of use: For example, it could be for research and development purposes, commercial use, or educational use. • Usage period: The period during which you can eat the sample. The item "Sample Provider" contains information about the company that provided the sample data.

[0142] Specifically, the item "Sample Provider" corresponds to the identification information of each provider shown in the "Provider ID" item in the user database. For example, a provider may register design data obtained by designing a device using the service of server 20 in the spacecraft sample database 213.

[0143] The item "Number of Uses" contains information on how often the sample data has been used.

[0144] Specifically, the item "Number of Uses" includes information such as the number of times requests for use have been made for the sample data. This allows for determining how often the sample data is being used, and this can be reflected in search rankings when users search for the sample data. Furthermore, the sample data and the user who registered the sample data (the user's business) may be evaluated based on the usage history of the sample data.

[0145] The item "Project Usage History" identifies the projects in which the sample data was used.

[0146] Specifically, the item "Project Usage Record" corresponds to the item "Project ID" in the Space Project Database 215, which will be described later. This allows for the evaluation of sample data and the user (or the user's business) who registered the sample data based on its actual use in space development projects.

[0147] Figure 7 shows the data structure of the astronaut database 214. The astronaut database 214 includes the following items: "Astronaut ID", "Name", "Affiliation", "Flight Record", and "Evaluation Value".

[0148] The "Astronaut ID" field contains information that identifies each astronaut.

[0149] The "Name" field contains information indicating the astronaut's name.

[0150] The "Affiliation" field indicates the astronaut's affiliation.

[0151] The item "Flight Record" contains information about the astronauts' flight records.

[0152] Specifically, the item "Flight Record" may be identified based on the following achievements made by the astronauts. • The duration of time spent in space aboard a spacecraft • Duration and content of the training Furthermore, the astronaut database 214 may register astronauts who have achieved a certain level of experience (for example, astronauts who have been certified as having accumulated a certain level of experience within a space development organization), and astronauts may not be registered in the astronaut database 214 until they reach that level of experience.

[0153] The "Evaluation Value" item is information that indicates the astronaut's evaluation.

[0154] Specifically, the item "Evaluation Value" may hold the results of an evaluation of the astronauts' flight performance using the following method. • The duration of time spent in space aboard a spacecraft • Duration and content of the training • Specialized knowledge, and tasks that can be performed on a spacecraft. By maintaining information on these astronauts, server 20 can identify potential personnel for space development projects (the space project database 215, described later).

[0155] Figure 8 shows the data structure of the Space Project Database 215. The Space Project Database 215 includes the following items: "Project ID", "Client", "Project Manager", "Project Participants", "Purpose / Goals", "Project Implementation Period", "Status", "Overall Evaluation Score", "Development Performance Score", "Operational Performance Score", "Project Budget", and "Insurance Premium".

[0156] The "Project ID" field is information that identifies each individual space development project.

[0157] The item "Client" is information that identifies the client that commissions a space development project.

[0158] The item "Project Manager" is information that identifies the person responsible for managing the space development project.

[0159] The item "Project Participants" is information that identifies the participants involved in the space development project.

[0160] Specifically, the item "Project Participants" includes information that identifies each party involved in the space development project, such as the device design company.

[0161] The "Purpose / Goals" section contains information that outlines the purpose and goals of a space development project.

[0162] Specifically, the item "Purpose and Objectives" includes information about the objectives and goals of a space development project, such as landing on a comet for comet exploration, collecting samples, and bringing them back to Earth.

[0163] The item "Project Implementation Period" contains information about the period designated for the implementation of a space development project.

[0164] The "Status" item contains information indicating the status of the space development project.

[0165] Specifically, the item "Status" includes the following information regarding the status of the space development project: • Under Development: The device is in the development stage to achieve its purpose and goals. • Project Formation: We are currently in the stage of selecting members to drive the space development project. • Finished: The project has been terminated. The "Overall Evaluation Score" item is information representing the results of an overall evaluation, which is an aggregation of scores obtained by evaluating space development projects from various perspectives.

[0166] Specifically, the item "Overall Evaluation Score" may be considered as an aggregation of various scores such as the "Development Performance Score" and "Operational Performance Score," which will be described later.

[0167] The "Development Performance Score" item is information that reflects the results of an evaluation of the allocation of development resources and development performance related to space development projects.

[0168] Specifically, the item "Development Performance Score" may be considered an evaluation value calculated based on information accumulated in the following various databases. • We have a track record of developing spacecraft using simulations provided by Server 20. • Development record of spacecraft development companies (number of projects, years, difficulty level, budget size, etc.) stored in the Development Spacecraft Database 219. • The development record of personnel from development companies, stored in the Space Development Human Resources Database 218. • Space projects the company has participated in in the past. For example, the company may be evaluated based on its track record of participating in important space projects promoted by the government or other public bodies. Alternatively, the evaluation method may be as follows: • The position (ranking) of a company compared to other companies. For example, development companies are ranked based on their development track record (number of projects, years, difficulty level, etc.), and those ranked higher are highly evaluated. • The spacecraft must meet the required quality standards (for example, meeting quality standards set by the government, etc., such as software code quality and durability quality). This is a comparison with other space development projects that have been implemented in the past and whose initial objectives have been determined. For example, even if the objective remains the same, improvements in spacecraft performance, the track record of the development company, and operational experience may lead to a project being evaluated as having a higher probability of success than past space development projects. The "Operational Performance Score" item is information that evaluates the operational performance of businesses participating in space development projects within those projects.

[0169] Specifically, the item "Operational Performance Score" may be considered an evaluation value calculated based on information accumulated in the following various databases. • Server 20 has a track record of conducting simulations of spacecraft operations. • Data stored in the Development Spacecraft Database 219, including operational records of development companies (number of projects, years, difficulty level, budget size, etc.) • Track record of operations carried out by personnel of development companies, stored in the Space Development Human Resources Database 218. • Space projects the company has participated in in the past. For example, the company may be evaluated based on its track record of participating in important space projects promoted by the government or other public bodies. Alternatively, the evaluation method may be as follows: • The position (ranking) within the overall picture compared to other businesses. For example, development companies are ranked based on their operational track record (number of projects, years, difficulty level, etc.), and those ranked higher are highly evaluated. • The spacecraft must meet the required quality standards (for example, meeting quality standards set by the government, etc., such as software code quality and durability quality). This is a comparison with other space development projects that have been implemented in the past and whose initial objectives have been determined. For example, even if the objective remains the same, improvements in spacecraft performance, the track record of the development company, and operational experience may lead to a project being evaluated as having a higher probability of success than past space development projects. The item "Project Budget" contains information on the scale of the project budget for space development projects.

[0170] The item "Insurance Premium" contains information about the insurance terms set for space development projects.

[0171] Specifically, the item "Insurance Premium" includes information on the terms and conditions (including premiums) of insurance policies of the following nature: • Insurance to cover damage to the spacecraft • Insurance aimed at compensating third parties, such as in the event of a spacecraft colliding with another satellite. Furthermore, insurance premiums may be set for each stage of a space development project, as follows: • Launching a spacecraft (there is a possibility of the launch itself failing, or the launch trajectory not being as intended and colliding with other spacecraft). • The spacecraft is a satellite or similar, and the mission is conducted in orbit (there is a possibility of malfunction due to spacecraft degradation, collisions with debris, etc.). • Missions assigned to spacecraft, such as exploration missions (for example, landing on a planet or a satellite in orbit around a planet to conduct exploration, collect samples, etc.) To calculate these insurance premiums, the scoring module 2047 uses the score evaluated for the space project as an indicator of the project's likelihood of success to calculate the premium.

[0172] Figure 9 shows the data structure of the design history database 216. The design history database 216 includes the following items: "Development ID", "Business Operator ID", "User ID", "Design Data Update Date and Time", "Design Data", "Simulation Results", "Evaluation Value", and "Project ID".

[0173] The "Development ID" field is information that identifies each device development.

[0174] The "Business ID" field is information that identifies the organization to which the user belongs.

[0175] Specifically, the item "Business ID" corresponds to the item "Business ID" in user database 211.

[0176] The "User ID" field is information that identifies each user.

[0177] Specifically, the item "User ID" corresponds to the item "User ID" in user database 211.

[0178] The item "Design Data Update Date and Time" contains information about when a user newly registered device design data or edited and saved registered design data.

[0179] The item "Design Data" refers to the data related to the design of the device.

[0180] Specifically, the item "Design Data" includes the following as design data: • Design drawings showing the structure of the device • A document defining the device specifications. • Test data obtained by testing the device in a simulated environment. The item "Simulation Results" contains information on the simulation results when the device related to the design data is operated under the constraints of the space environment.

[0181] Specifically, the item "Simulation Results" includes information on the results of simulations that refer to the constraints in the space environment (Constraint Database 212) to determine whether the device related to the design data conforms to those constraints, or whether it cannot operate in the space environment based on those constraints. For example, the communication specifications of the device related to the design data may exceed the performance allowed in the space environment, making it unusable in space. Also, the power limitations available in the space environment may mean that the design data for a ground-based device is not suitable.

[0182] The item "Evaluation Value" is information that shows the score obtained by evaluating the device related to the design data.

[0183] Specifically, the item "Evaluation Value" may include information resulting from the evaluation of the device related to the design data, as follows: • The device must conform to the constraints of the space environment (Constraint Database 212). • The device must have been designed by a highly-rated user (user database 211). • Devices have been viewed by users. • Devices have been selected for projects. • User evaluations of the device The "Project ID" field is information that identifies the space development project associated with the device related to the design data.

[0184] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0185] Figure 10 shows the data structure of the matching database 217. The matching database 217 includes the items "Matching ID", "Project ID", "First Business Operator", "Second Business Operator", "Purpose", "Matching Date and Time", and "Evaluation".

[0186] The "Matching ID" field is information that identifies each match between users or businesses.

[0187] The "Project ID" field is information that identifies each individual space development project.

[0188] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0189] The item "First Business Operator" is information that identifies the first business operator involved in the matching process.

[0190] The item "Second Business Operator" is information that identifies the second business operator involved in the matching process.

[0191] Specifically, the item "Second Business Operator" may correspond to the item "Business Operator ID" in user database 211. Furthermore, it may include information on three or more businesses, not just two businesses such as the first and second businesses.

[0192] The "Purpose" field contains information about the purpose of the matching process.

[0193] Specifically, the item "Purpose" may include information about the purpose, such as the following: • Development of specific devices required for space development projects The "Matching Date and Time" field contains information about when the match was made.

[0194] Specifically, the item "Matching Date and Time" is information about the timing at which a match is determined to have been made, for example, when communication between the businesses involved in the matching process begins.

[0195] The "Rating" item contains information about each user's rating of the matching service.

[0196] Specifically, the "Evaluation" item should include an evaluation of the matching process based on the contributions each matched business made to the project (e.g., developing a device), and may also include information on the evaluation results.

[0197] Figure 11 shows the data structure of the Space Development Personnel Database 218. The Space Development Personnel Database 218 includes the following items: "User ID", "Company ID", "Participating Projects", "Development Achievements", "Operational Achievements", and "Publication Achievements".

[0198] The "User ID" field is information that identifies each user.

[0199] Specifically, the item "User ID" corresponds to the item "User ID" in user database 211.

[0200] The "Business ID" field contains information that identifies the organization the user belongs to, as well as information about the period during which they belonged to that organization.

[0201] Specifically, the "Business ID" field corresponds to the "Business ID" field in user database 211. In this way, the "Business ID" field indicates the user's history of belonging to an organization.

[0202] The "Participating Projects" item contains information identifying the space projects in which the user participated, as well as information about the period of participation.

[0203] The "Development Achievements" item contains information identifying the spacecraft developed by the user, as well as information about the period of development.

[0204] The "Operational Performance" item contains information identifying the space projects in which the user participated in operations, as well as information about the period during which those operations took place.

[0205] The "Publication Record" item contains information on the achievements of space development that have been published through papers, patents, presentations, etc.

[0206] Specifically, the item "Publication Record" includes information on published papers and other technical documents, meetings attended, materials presented at those meetings, and information on the dates of those presentations.

[0207] Figure 12 shows the data structure of the Development Spacecraft Database 219. The Development Spacecraft Database 219 includes the following items: "Spacecraft ID", "Project ID", "Developer ID", "Developer User ID", "Development Period", "Manufacturing Equipment / Processing Equipment", "Utilization History Projects", "Specifications / Performance", and "Demonstration Test Results".

[0208] The "Spacecraft ID" field is information that identifies each developed spacecraft.

[0209] The "Project ID" field is information that identifies each space development project that served as the impetus for the development of a spacecraft.

[0210] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0211] The item "Developer ID" is information that identifies the organization carrying out the development.

[0212] Specifically, the item "Developer ID" corresponds to the item "Business ID" in user database 211.

[0213] The "Developer User ID" field is information that identifies each user performing development work.

[0214] Specifically, the item "Developer User ID" corresponds to the item "User ID" in User Database 211 and the item "User ID" in Space Development Personnel Database 218.

[0215] The item "Development Period" contains information about when the spacecraft was developed.

[0216] The item "Manufacturing Equipment / Processing Equipment" is information about the manufacturing equipment or processing equipment used in the production of space machines.

[0217] Specifically, the item "Manufacturing Equipment / Processing Equipment" may include the following information. · Information about the manufacturer that produced the manufacturing equipment or processing equipment · Information identifying the performance of the equipment, such as the model number of the manufacturing equipment or processing equipment The item "Utilization Record Project" is information identifying space development projects in which the developed space machines have been utilized.

[0218] Specifically, the item "Utilization Record Project" corresponds to the item "Project ID" in the space project database 215.

[0219] The item "Specifications / Performance" is information about the specifications, performance, etc. of the space machine.

[0220] Specifically, the item "Specifications / Performance" may include information about the specifications and performance in line with the purpose of the project in which the space machine is used. For example, when the space machine is for planetary exploration, it includes information such as the size, cruising performance, power generation capacity, etc. of the space machine The item "Demonstration Test Results" is information about the results of the demonstration tests conducted on the space machine.

[0221] Specifically, the item "Demonstration Test Results" may include information such as the conditions of the demonstration tests defined in the space development project, the schedule of the tests, and the results of the demonstration tests.

[0222] Figure 13 is a diagram showing the data structure of the insurance application history database 220. The insurance application history database 220 includes the item "Application ID", the item "Project ID", the item "Applicant", the item "Application Date and Time", the item "Application Details", and the item "Insurance Payment".

[0223] The item "Application ID" is information identifying each insurance application.

[0224] The "Project ID" field is information that identifies the space development project related to the insurance application.

[0225] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0226] The "Applicant" field contains information that identifies the user who is applying for insurance.

[0227] The item "Application Date and Time" contains information about when the insurance application was received.

[0228] The item "Application Details" contains information such as the terms and conditions of the insurance application.

[0229] The item "Insurance Payment" contains information such as whether or not an insurance payment was made, and if so, the amount paid.

[0230] Figure 14 shows the data structure of the financial support history database 221. The financial support history database 221 includes the following items: "Financial Support ID", "Project ID", "Type", "Funder", "Date and Time of Provision", "Provision Conditions", and "Status".

[0231] The item "Financial Support ID" is information that identifies each instance of financial support provided to a space development project.

[0232] The "Project ID" field is information that identifies space development projects receiving financial support.

[0233] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0234] The "Type" field contains information about the type of financial assistance provided.

[0235] Specifically, the item "type" includes information of the following types. · Financing · Investment · Donation The item "fund provider" is information for identifying the business operator that provided financial support.

[0236] The item "provision date and time" is information on the time when financial support was provided.

[0237] The item "provision conditions" is information on the conditions of financial support.

[0238] Specifically, the item "provision conditions" includes the following information as the conditions of financial support · In the case of financing, interest rate, repayment period, etc. · In the case of investment, amount, benefits for investment, etc. The item "status" is information on the status of financial support.

[0239] Specifically, the item "status" includes the following information as the status of financial support. · Financing has been conducted but the repayment period has not yet arrived · Repayment for financing has been completed · Payment for investment has been made Figure 15 is a diagram showing the data structure of the rights transaction history database 222. The rights transaction history database 222 includes the item "transaction ID", the item "project ID", the item "rights issuing entity", the item "number of rights issued", the item "seller", the item "purchaser", the item "transaction price", the item "transaction quantity", and the item "transaction date and time".

[0240] The item "transaction ID" is information for identifying each transaction when rights for which benefits can be obtained by investment in a space development project are traded.

[0241] The item "project ID" is information for identifying the space development project to which the rights transaction pertains.

[0242] Specifically, the item "Project ID" corresponds to the item "Project ID" in Space Project Database 215.

[0243] The item "Right-issuing entity" contains information about the entity that issues the rights.

[0244] Specifically, the item "Rights Issuer" could refer to a business operator (e.g., a management contractor, a management manager, etc.) that solicits funding for a space development project, which may be the issuer of the rights.

[0245] The item "Number of Rights Issued" contains information on the total number of rights issued.

[0246] Specifically, the item "Number of Rights Issued" includes information on the number of rights issued, which will be set as appropriate by the rights issuer in accordance with the amount of funds to be raised.

[0247] The item "Seller" contains information about the seller in the transaction of the rights.

[0248] The item "Purchaser" contains information about the buyer in the transaction of the rights.

[0249] The item "Transaction Price" contains information about the transaction price of the right.

[0250] The item "Transaction Quantity" contains information about the transaction quantity of the rights.

[0251] The "Transaction Date and Time" field contains information about the time when the transaction of the rights was completed through the order.

[0252] <3 Operation (First Embodiment)> Figure 16 shows the process flow for performing simulations based on design data and constraints in the space environment.

[0253] As described above, the server 20 is configured to store the parameters of each item that affects the control of the equipment in the space environment in the constraint database 212 of the storage unit 202. The constraint database 212 includes at least one of the following parameters as parameters for each item: gravity parameters, temperature parameters, communication parameters, power parameters, air parameters, and radiation parameters.

[0254] In step S1121, the simulation processing module 2045 of the server 20 outputs a screen to the terminal 10 for registering or editing design data related to the design of the device.

[0255] Here, the devices include at least one of the following: devices for use inside the space colony (including drones for use inside the space colony), devices for use outside the space colony, satellites, and exploration equipment.

[0256] Furthermore, the design data includes at least one of the following: data defining the device specifications, or data representing the device design drawings.

[0257] In step S1111, the control unit 190 of terminal 10 displays an operation screen on the display 132 and accepts from the user an operation to register design data including ground machine data, or an operation to edit the contents of already registered design data. The control unit 190 sends information indicating the user's operation to the server 20.

[0258] In step S1123, the simulation processing module 2045 of the server 20 obtains the registration details of the design data received from the terminal 10, or the edited details of the design data that has already been registered.

[0259] In step S1125, the simulation processing module 2045 of the server 20 refers to the constraint database 212 and performs a simulation of the device from the design data operating in the space environment, based on the parameters of each item that affect the control of the equipment in the space environment.

[0260] Specifically, the simulation processing module 2045 simulates the operation of devices in a space environment, calculating the operation of each device in a group. For example, it simulates the movement of multiple devices exploring the lunar surface as a group, while simultaneously simulating the processes required to achieve the exploration objectives.

[0261] For example, one could assign a specific role to each device exploring the lunar surface, such as a device for surveying, a device for collecting samples from the ground, and then simulate the movement of these devices while they communicate with each other according to their respective roles.

[0262] Furthermore, multiple devices may be coordinated both inside and outside the spacecraft. For example, multiple drones could be prepared inside the spacecraft, communicate with each other, and transport objects.

[0263] Furthermore, the operation of the devices may be simulated taking into account the people (such as astronauts) staying in the spacecraft. For example, a simulation may be performed to show how a device that transmits the location of a person and an onboard drone work together to ensure the drone reaches the person's location.

[0264] In step S1127, the simulation processing module 2045 of the server 20 outputs a screen displaying the simulation results to the terminal 10.

[0265] The simulation processing module 2045 may perform a simulation to determine whether the device based on the acquired design data meets the requirements for the space environment, and then present the result of this determination to the terminal 10.

[0266] The simulation processing module 2045 displays a 3D model of the device corresponding to the acquired design data, and may also display the results of the determination in association with the objects that make up the displayed 3D model.

[0267] The simulation processing module 2045 identifies each parameter item corresponding to the unmet requirements when it determines that the device relating to the acquired design data does not meet the requirements in the space environment. The simulation processing module 2045 may also present each parameter item corresponding to the identified unmet requirements when the device does not meet the requirements in the space environment.

[0268] The simulation processing module 2045 may determine whether the acquired design data satisfies the requirements in the space environment by prompting the server 95 of the large-scale language model service to respond whether or not the requirements in the space environment are met. For example, the design data may be prepared as specification data and sent to the server 95 of the large-scale language model service along with information on constraints in the space environment (constraint database 212), and the above response may be generated by giving the server 95 a prompt to that effect. The simulation processing module 2045 then sends the response generated in this manner to the terminal 10.

[0269] The simulation processing module 2045 may determine, based on communication constraints in the space environment, whether or not the device related to the acquired design data can perform the expected control, in order to determine that it does not meet the requirements in the space environment.

[0270] The simulation processing module 2045 may, based on the acquired design data, identify one or more specifications permissible in the space environment based on the spacecraft sample database 213. For example, it may identify sample data corresponding to the device the user wants to design by comparing the device attributes shown in the design data with the "Attributes" item in the spacecraft sample database 213.

[0271] The simulation processing module 2045 may transmit one or more specifications identified as sample data to the terminal 10 and present them to the user of the terminal 10. In this case, the simulation processing module 2045 may determine the priority of the sample data from the spacecraft sample database 213 according to the sample provider, the number of times it has been used, the presence or absence of a project in which it has been used, etc., and display them on the terminal 10. For example, the more frequently a sample data has been used, the more likely it is to be recommended to the user. This allows the user to easily obtain design data for a device that conforms to the constraints of the space environment. The user can then design using the sample data that conforms to the constraints of the space environment as a starting point.

[0272] In step S1113, terminal 10 displays the simulation results on display 132.

[0273] Figure 17 shows the process flow for evaluating space development operators.

[0274] In step S1221, the matching processing module 2046 of the server 20 refers to the design history database 216 and the space project database 215, calculates the score of the operators developing spacecraft, and updates the user database 211.

[0275] In step S1211, the control unit 190 of terminal 10 receives an operation from the user to search for candidate businesses to participate in the space project. For example, the user could be the administrator of the space project, the client, or a business that develops devices. In step S1223, the matching processing module 2046 of the server 20 identifies matching candidates based on the scores of businesses identified in the user database 211. For example, it may identify users with high evaluation scores, or businesses to which such users belong, or businesses related to the purpose of the space project. The matching processing module 2046 presents the user of terminal 10 with a screen for matching, including information on the identified candidate businesses.

[0276] In step S1213, the control unit 190 of terminal 10 displays a matching screen on the display 132. The control unit 190 accepts an operation from the user to specify a candidate business operator.

[0277] In step S1227, the matching processing module 2046 of the server 20 updates the matching database 217 according to the information of the business operator specified by the user of the terminal 10. For example, the server 20 enables the matching business operators to send and receive messages, process payments, share files, etc.

[0278] <4. Screen Example (First Embodiment)> Figure 18 shows an example of a screen for searching for businesses involved in space development projects.

[0279] Operation screen 1000 provides users with screens for managing space projects and screens that provide a development environment for spacecraft.

[0280] In Figure 13, the operation screen 1000 shows an example of a screen that provides support for the composition of project members for space project managers. Figures 14 to 16 show examples of screens that provide support for businesses developing spacecraft.

[0281] The user information display area 1002 is an area that displays information about users who log in to the services provided by the server 20.

[0282] The space project display area 1004 is an area that displays detailed information about the space project.

[0283] The space project display area 1004 may display information managed in the space project database 215 as detailed information about the space project.

[0284] The switching operation reception unit 1006 is an operating component that receives an operation to switch the space project to which the details are to be displayed.

[0285] The member candidate display area 1008 is an area that displays information about candidates for the space project.

[0286] The member candidate display area 1008 corresponds to the processing shown in step S1223 of Figure 12.

[0287] The candidate details display area 1010 is an area that displays the details of the candidate.

[0288] The candidate details display area 1010 may refer to the user database 211 and display information such as the candidate business operator and the user information of that business operator.

[0289] The participation request operation reception unit 1012 is an operating component that receives requests from the administrator of a space project to candidates to participate in the space project.

[0290] The participation request operation reception unit 1012 corresponds to processes such as step S1213 in Figure 12.

[0291] The participating members display area 1014 is an area that displays a list of information about businesses participating in the space project.

[0292] The participant display area 1014 may also display information about participants in the space project by referring to the space project database 215.

[0293] The participant details display area 1016 is an area that displays the details of the participants.

[0294] The participant details display area 1016 may refer to the user database 211 and display information such as the participating businesses and their users.

[0295] The participation operation reception unit 1018 is an operation component that receives operations from the administrator to join or leave a project.

[0296] The participation operation reception unit 1018 may display the status of participation in the project on a button, as shown in the figure.

[0297] Figure 19 shows an example of a simulation screen where multiple spacecraft are controlled as a swarm in a coordinated manner.

[0298] The simulation display area 1020 is an area that displays a screen simulating the operation of one or more spacecraft in a space environment.

[0299] The simulation display area 1020 may be configured to facilitate verification of the simulation results by displaying the conditions of the space environment (in the illustrated example, a simulation of the movement of the exploration rover), an object corresponding to one or more spacecraft, and the movement route of that object, as shown in the figure.

[0300] The device list display area 1022 is an area that displays a list of devices to be operated by the simulation.

[0301] The device list display area 1022, in the illustrated example, shows a situation where each device communicates with others to control multiple devices for planetary surface exploration (each device may be given a different role, or it may be given the same role, such as sample collection).

[0302] The first device display area 1024 is an area for displaying details of the first device.

[0303] The second device display area 1026 is an area for displaying details of the second device.

[0304] The third device display area 1028 is an area for displaying details of the third device.

[0305] The exploration location designation reception unit 1030 is an operating member that accepts the designation of the location to be explored.

[0306] The exploration location designation reception unit 1030, for example, if the location is the lunar surface, accepts the designation of coordinates on a lunar surface map and reads the terrain information for those coordinates.

[0307] The results display area 1032 is an area that displays a summary of the simulation results.

[0308] As shown in the figure, the results display area 1032 shows the constraints in the space environment and displays a summary of whether each device is operating in accordance with those constraints.

[0309] The first object 1034 is an object that corresponds to the first device and is placed in a virtual space that simulates the space environment.

[0310] The second object, 1036, is an object that corresponds to the second device and is placed in a virtual space that simulates the space environment.

[0311] The third object, 1038, is an object that corresponds to the third device and is placed in a virtual space that simulates the space environment.

[0312] Figure 20 shows an example of a screen that simulates whether a design is suitable for the space environment based on design data.

[0313] The registration operation reception unit 1040 is an operating component that receives operations from users to upload design data.

[0314] The registration operation reception unit 1040 can accept uploads of design data for ground vehicles from users, as well as uploads of design data for space vehicles. The design data may include not only specifications but also information on 3D models corresponding to design drawings.

[0315] The registered data list display area 1042 is the area that displays the uploaded design data.

[0316] The design data display area 1044 is an area that displays the details of the design data.

[0317] The simulation result display area 1046 is an area that displays the simulation results for the uploaded design data, taking into account the constraints in the space environment.

[0318] The simulation result display area 1046 corresponds to step S1125 in Figure 11, etc. As shown in the figure, it displays details of the failure to meet the constraint conditions.

[0319] The sample data display area 1048 is the area that displays candidate sample data.

[0320] The sample data display area 1048 may, as described above, display sample data identified from the spacecraft sample database 213 according to the purpose of the device (e.g., exploration) indicated in the design data, and accept user selection.

[0321] The first sample data display area 1050 is an area for displaying candidates for the first sample data.

[0322] The first sample data display area 1050 may accept user requests for the sample data, display the usage conditions for the sample data to the user, and accept applications for use (such as purchasing the sample data).

[0323] The second sample data display area 1052 is an area for displaying candidates for the second sample data.

[0324] Figure 21 is an example of a screen that displays simulation results on a 3D model based on design data.

[0325] The 3D model display area 1054 is the area that displays a 3D model of the user's design data.

[0326] Warning display area 1056 is an area that displays objects in the three-dimensional model that do not conform to the constraints, as well as details of the constraints that do not conform, according to the constraints of the space environment.

[0327] As shown in the illustration, the warning display area 1056 indicates that the constraints are not met in terms of "power" and "communication" in relation to a part of the three-dimensional model. The three-dimensional model is composed of multiple objects, and each object is managed with attributes such as its role (for example, the name of a communication unit). The server 20 may identify objects that do not meet the constraints according to the attributes of these objects and display them in relation to the content of the constraints.

[0328] <5 Operation (Second Embodiment)> Figure 22 shows the process flow for calculating a score that evaluates a space project.

[0329] In step S2221, the score calculation module 2047 of server 20 refers to various databases of each stakeholder involved in the space project, calculates the score of the space project according to the evaluation criteria, and updates the space project database 215.

[0330] The following explains in detail how the score calculation module 2047 calculates the score.

[0331] As described above, the simulation processing module 2045 of server 20 provides users of development companies with the processing to perform simulations of what would happen if the spacecraft design data were operated in a space environment, and to respond with the simulation results.

[0332] Server 20 stores information on the development track record of spacecraft based on simulations in the design history database 216, as information on spacecraft developers, in the memory unit 202.

[0333] The score calculation module 2047 refers to the design history database 216 and evaluates the likelihood of success of a space development project based on information about the developer's simulation-based development track record. For example, it calculates an evaluation value for the space development project in which the developer participates, based on track records such as the number of simulation-based development projects, the number of spacecraft designed to be operational in space through simulation, and the number and percentage of developed spacecraft that meet predetermined quality standards.

[0334] Server 20 stores in its memory unit 202 at least one of the following for development companies: information on the results of spacecraft demonstration tests (development spacecraft database 219) or information on their participation in space projects (space project database 215, space development personnel database 218).

[0335] The score calculation module 2047 of server 20 evaluates the likelihood of success of a space development project based on at least one of the following: information on the track record of spacecraft demonstration tests or information on the track record of participation in space projects. For example, the score calculation module 2047 may calculate an evaluation value that assesses the likelihood of success of a space project based on the number of spacecraft demonstration tests, the number of space projects participated in, the scale of the space projects participated in, and the entity responsible for the project (e.g., whether or not it is a government-led space project).

[0336] Server 20 stores, in its memory unit 202, information on space personnel, specifically information on the development company's personnel, including at least one of the following: information on the development track record of the development company's personnel, or information on the development company's personnel's track record of participating in space projects (Space Development Personnel Database 218). The score calculation module 2047 may evaluate the likelihood of success based on at least one of the information on the development track record of the development company's personnel, or information on the development company's personnel's track record of participating in space projects.

[0337] Server 20 stores information on astronauts' flight records as space personnel information in the astronaut database 214 in the memory unit 202. The score calculation module 2047 may evaluate the likelihood of success based on the astronauts' flight record information. For example, the score calculation module 2047 may assign a better score to a space project in which an astronaut participates if the astronaut has extensive flight experience, has participated in many space development projects, or has a large budget for a space development project in which the astronaut has participated.

[0338] Server 20 stores information about the spacecraft's performance in the spacecraft development database 219 in its memory unit 202. The score calculation module 2047 may evaluate the likelihood of success of a space project based on the information about the spacecraft's performance. For example, the better the performance of the spacecraft (such as its reliability, sensing range, and navigation performance), the higher the likelihood that the space development project will achieve its intended objectives and succeed, and the better the score of the space development project may be.

[0339] Server 20 stores information about spacecraft, including manufacturing equipment, processing equipment, and other equipment used to create spacecraft, in the spacecraft development database 219 in its memory unit 202. The score calculation module 2047 may evaluate the likelihood of success of a space development project based on the information about the equipment used to create the spacecraft. For example, the better the performance of the manufacturing equipment and processing equipment used to create the spacecraft (such as processing precision), the better the score of the space development project may be.

[0340] The score calculation module 2047 of server 20 may relatively evaluate the likelihood of success of a space project by comparing information on stakeholders of multiple space projects. For example, if there is a certain level of difference in the track record of stakeholders of each space project, the score calculation module 2047 may relatively evaluate the score of each space project, with a higher score indicating greater track record.

[0341] The score calculation module 2047 of server 20 may evaluate the likelihood of success of a space project based on whether the spacecraft in the space project meets predetermined criteria. For example, the government or other authority may set standards for software code quality, equipment durability, etc., and the score calculation module 2047 may calculate a score for the space project based on whether or not these quality standards are exceeded.

[0342] In the storage unit 202 of server 20, information on whether each space project achieved its intended objectives is stored in the space project database 215, associated with the information of each space project. The score calculation module 2047 may evaluate the likelihood of success of the first space project based on information on at least one of the parties involved in the first space project or the spacecraft, and information on at least one of the parties involved in a second space project that was carried out in the past, as well as information on whether the second space project achieved its intended objectives. For example, for the space development project under evaluation, the score of the space project may be calculated by comparing the results of similar space development projects carried out in the past (whether the intended objectives were achieved), the information on the participants and spacecraft in those past space projects, and the information on the participants and spacecraft in the space development project under evaluation. For example, if the performance of the spacecraft is better and the operational track record is more extensive than that of past successful space projects, the score of the space project may be set higher than the score of past space projects.

[0343] In step S2223, the score calculation module 2047 of server 20 calculates the insurance premium required to carry out the space project according to the space project's score, budget, and content, and updates the space project database 215. For example, the score calculation module calculates the insurance premium so that the better the space project's score, the lower the premium. Alternatively, the score calculation module 2047 may also increase the required insurance premium as the space project's budget increases.

[0344] The score calculation module 2047 of server 20 outputs a screen to the terminal 10 of the person involved in the space project, displaying the evaluation results for the space project.

[0345] Figure 23 shows the process flow for accepting insurance applications for space projects.

[0346] In step S2321, the transmission control module 2042 of the server 20, in response to access from the terminal 10, refers to the space project database 215 and outputs an operation screen to the terminal 10 that accepts insurance applications, including space project information, space project scores, and space project insurance premium information.

[0347] Server 20 accepts applications for insurance for the space project from those involved in the space project, while displaying information such as the insurance premium, coverage details, and other insurance conditions for the space project on a screen that shows the evaluation results of the space project.

[0348] In step S2311, terminal 10 displays information about the space project, information about the space project score, and information about the insurance conditions on its operation screen, and accepts an operation from the user to apply for insurance.

[0349] In step S2323, the transaction acceptance module 2048 of the server 20 updates the insurance application history database 220 in response to the insurance application. The transaction acceptance module 2048 stores in the insurance application history database 220 of the storage unit 202 that an insurance application has been made for the space project, in response to the operation to apply for insurance. The transaction acceptance module 2048 outputs to the terminal 10 that the application has been completed.

[0350] In step S2313, terminal 10 displays on its screen that the application for insurance for the space project has been completed.

[0351] Figure 24 shows the processing flow for accepting transactions related to financing space projects.

[0352] In step S2421, the transaction acceptance module 2048 of the server 20, in response to access from the terminal 10, refers to the space project database 215 and displays information about the space project, the score of the space project, and the loan or investment conditions, and outputs an operation screen that accepts the operation to provide a loan. For example, the better the score of the space project, the more favorable the loan conditions (e.g., a lower repayment interest rate) or investment conditions (e.g., a higher valuation of the space project) may be set for the participants in the space project (e.g., the client or operator of the space project).

[0353] The transaction acceptance module 2048 of server 20 outputs a screen displaying the evaluation results to the terminal 10 of the user making the investment or loan. The transaction acceptance module 2048 accepts the operation from the user making the investment or loan to invest in or lend money for the space project on the screen displaying the evaluation results. In response to the operation of the user making the investment or loan, the transaction acceptance module 2048 stores information about the user making the investment or loan for the space project and information about the conditions of the investment or loan in the financial support history database 221 of the storage unit 202.

[0354] Server 20 executes a step in which it determines the benefits to be granted to users who invest in or finance a space project if the project generates revenue through commercial activities, based on the revenue. For example, the benefits may include distributing dividends from the revenue, and Server 20 may determine the percentage of the revenue to be distributed as dividends and grant dividends to the invested users in proportion to their right to receive dividends.

[0355] In step S2411, terminal 10 displays information such as space project information, score information, and loan or investment conditions on its operation screen, and accepts an operation from the user to provide a loan or investment in the space project.

[0356] In step S2423, the transaction acceptance module 2048 of the server 20 updates the financial support history database 221 according to the loan or investment conditions in response to the user's operation to make a loan or investment. The transaction acceptance module 2048 outputs to the terminal 10 that the acceptance of the loan or investment has been completed.

[0357] In step S2413, terminal 10 displays on its screen that it has accepted a loan or investment in a space project.

[0358] Figure 25 shows the processing flow for accepting transactions related to investments in space projects.

[0359] In step S2521, the transaction acceptance module 2048 of the server 20, in response to access from the terminal 10, refers to the space project database 215 and displays information about the space project, the score of the space project, and the conditions for trading the rights related to the investment, and outputs an operation screen to the terminal 10 that accepts the operation to trade the rights.

[0360] Server 20 stores information in the rights transaction history database 222 of the storage unit 202 regarding the right to receive benefits based on revenue generated when a space project generates revenue through commercial activities. The transaction acceptance module 2048 of Server 20 grants rights to users who make investments or loans and then executes steps to allow users to trade rights with each other. For example, the transaction acceptance module 2048 may display information on orders to sell rights (selling price and quantity sold) and information on orders to purchase rights (purchase price and quantity purchased), and accept the specification of the transaction price and transaction quantity from the user of Terminal 10.

[0361] In step S2511, terminal 10 displays information such as space project information, score information, and conditions for trading rights on its operation screen, and accepts an operation from the user to trade rights.

[0362] In step S2523, the transaction acceptance module 2048 of the server 20 updates the rights transaction history database 222 in response to each user's operation to trade rights. The transaction acceptance module 2048 outputs to the terminal 10 that the rights transaction has been completed.

[0363] In step S2513, terminal 10 displays on its screen that the transaction for the rights related to the space project has been completed.

[0364] <6. Screen Example (Second Embodiment)> Figure 26 shows an example of a screen for accepting insurance applications for space projects.

[0365] Operation screen 2600 is the screen used to accept applications for insurance related to space projects.

[0366] The operation screen 2600 corresponds to the example in Figure 23.

[0367] Score display area 1058 is the area that displays the score calculated for the space project.

[0368] Detailed display area 1060 is the area that displays the details of the space project's score.

[0369] The detailed display area 1060 displays information such as the score of the space project, the basis for calculating the score (for example, if the score is relatively good compared to other space projects, this fact is indicated), and insurance conditions including premiums, based on the space project database 215.

[0370] The application operation reception unit 1062 is an operating component that receives applications for insurance.

[0371] As shown in the diagram, the application operation reception unit 1062 accepts applications for insurance while displaying information on the screen such as the insurance underwriter's information, detailed information on the space project (space project display area 1004), and information on the space project's score (details display area 1060).

[0372] The confirmation operation reception unit 1064 is an operating component that receives operations to confirm information about participants in space development projects that are presenting scores.

[0373] The confirmation operation reception unit 1064 identifies project participants based on the space project database 215 in response to user operations and responds with information about the project participants.

[0374] The confirmation operation reception unit 1066 is an operating component that receives an operation to confirm the information of the insurance underwriter.

[0375] The "Other Projects" display area 1068 is an area that displays information about other space development projects similar to the space development project whose score is being displayed.

[0376] The other project display area 1068 displays details and score information for the identified projects, based on the content of the project, after the server 20 identifies similar projects. For example, the server 20 identifies similar space projects based on information such as the purpose of the space project, information on the participants in the space project, and the budget size of the space project. The server 20 may also identify other projects similar to the space project whose score is to be displayed by prompting the server 95 of the large-scale language model service to identify similar space projects.

[0377] Score display area 1070 is an area that displays details of the scores for other similar space projects.

[0378] The confirmation operation reception unit 1072 is an operating component that receives operations to confirm details of other similar space projects.

[0379] The confirmation operation reception unit 1072 displays information such as the project client and project manager in response to the user's operation.

[0380] Figure 27 shows an example of a screen for accepting transactions related to financing space projects.

[0381] Operation screen 2700 is the screen that accepts operations for making loans or investments.

[0382] The operation screen 2700 corresponds to the example in Figure 24.

[0383] The loan and investment operation reception unit 1074 is an operating component that receives operations for loans or investments in space projects.

[0384] The loan and investment operation reception unit 1074 displays a screen that accepts the specification of loan or investment conditions in response to user operations, and accepts the user's specification of the loan amount and other loan conditions, or the investment amount and other investment conditions.

[0385] The confirmation operation reception unit 1076 is an operating component that accepts user operations to confirm the loan or investment history in other similar space projects.

[0386] The confirmation operation reception unit 1076 displays information such as the amount of financing or investment made in other similar space projects, the timing, and the information of the funders, in response to the user's operation.

[0387] Figure 28 shows an example of a screen for accepting transactions related to investments in space projects.

[0388] Operation screen 2800 is the screen that accepts transactions for the right to receive revenue from space projects.

[0389] The operation screen 2800 corresponds to the example in Figure 25.

[0390] Copyright notice area 1078 is an area for displaying information about the right to receive revenue from space projects.

[0391] The confirmation operation reception unit 1080 is an operating component that accepts operations to confirm the issuance status of the right to receive a share of the profits as a reward for receiving benefits from the space project.

[0392] The confirmation operation reception unit 1080, in response to the user's operation, refers to the rights transaction history database 222 and responds with information such as the number of rights issued.

[0393] Transaction display area 1082 is an area that displays the transaction status of rights.

[0394] Order display area 1084 is an area that displays the order status for the buying and selling of rights issued for space projects.

[0395] The order display area 1084 refers to the rights transaction history database 222 and displays the price and quantity of sell orders and buy orders to serve as a reference for user transactions.

[0396] The order operation reception unit 1086 is an operating component that receives orders for rights.

[0397] The order processing unit 1086 accepts the specified selling price and quantity for sell orders, and the specified purchase price and quantity for buy orders. The order processing unit 1086 may also accept orders with a limit price (or stop-loss price).

[0398] The confirmation operation reception unit 1088 is an operating component that receives operations to confirm the trading status of rights issued for other similar space projects.

[0399] The confirmation operation reception unit 1088 displays information such as the transaction price of rights related to other similar space projects in response to user operations.

[0400] <Third Embodiment> The third embodiment will be described below. In the third embodiment, the matching of personnel involved in space development with companies that conduct space development will be supported, thereby facilitating personnel changes and recruitment by companies. This will help to place personnel involved in space development in suitable roles, further promoting space development.

[0401] <7 Data Structure (Third Embodiment)> Figure 29 shows the data structure of the talent matching database 223. The talent matching database 223 includes the following items: "Offer ID", "Job Seeker User ID", "Compensation Score", "Annual Salary Equivalent", "Career Information", "Employer ID", "Employer User ID", "Matching Date and Time", and "Status".

[0402] The "Offer ID" field is information that identifies each offer related to matching a job-seeking user with a job-posting business.

[0403] The item "Job Seeker User ID" is information that identifies the user seeking employment.

[0404] Specifically, the item "Job Seeker User ID" corresponds to the item "User ID" in user database 211.

[0405] The "Compensation Score" item is information about the compensation evaluated for the job-seeking user.

[0406] Specifically, the item "Reward Score" corresponds to the item "Reward Score" in user database 211.

[0407] The "Annual Salary Equivalent" item is information about the compensation evaluated for job-seeking users, converted into an annual salary.

[0408] Specifically, the item "Annual Income Equivalent" corresponds to the item "Annual Income Equivalent" in user database 211.

[0409] The "Career Information" field contains information about the job seeker's career history.

[0410] Specifically, the "Career Information" item includes the following career information: • Resume information edited by the job seeker user • Career information generated by server 20, etc., based on information stored in various databases such as the space development personnel database 218, the design history database 216, and the user database 211. Career information may also be generated by instructing the server 95 of the large-scale language model service to summarize information showing the careers of job-seeking users based on the information stored in various databases. The item "Job Posting Company ID" is information that identifies the job posting company.

[0411] Specifically, the item "Recruiting Business ID" corresponds to the item "Business ID" in user database 211, etc.

[0412] The item "Job Posting User ID" is information that identifies the user at the job posting company.

[0413] Specifically, the item "Job Posting User ID" corresponds to the item "User ID" in user database 211.

[0414] The "Matching Date and Time" field contains information about the timing when a job seeker user and a recruiting business were matched.

[0415] Specifically, the item "Matching Date and Time" may include information about the timing, such as the following: • The timing when a job seeker initiates a job change request and a recruiting company makes an offer. • When a recruiting company publishes information about the type of person they are looking for, and a job seeker applies, • Scheduling interviews and determining the timing of job offers between job seekers and employers. The "Status" field provides information about the matching status between job-seeking users and employers.

[0416] Specifically, the "Status" field may include the following information as a representation of the matching status: Matching successful, interview schedule to be arranged. • Interview completed, employment under consideration. • In conclusion, it was not adopted. • In conclusion, the decision was made to hire. Figure 30 shows the data structure of the desired personnel database 224. The desired personnel database 224 includes the following items: "Job ID", "Employer ID", "Job Title", "Personnel Requirements", "Annual Salary Range", "Validity Period", "Expected Compensation Range", and "Status".

[0417] The "Job ID" field is information that identifies each job posting, where the employer registers information about the type of personnel they are looking for.

[0418] The item "Job Posting Company ID" is information that identifies the job posting company.

[0419] Specifically, the item "Recruiting Business ID" corresponds to the item "Business ID" in user database 211, etc.

[0420] The item "Job Openings" contains information about the job titles and duties offered by the recruiting company in relation to space development.

[0421] The "Personnel Requirements" section contains information on the criteria and guidelines for hiring personnel, in light of the job title and duties being advertised.

[0422] Specifically, the item "Requirements for personnel" may include the following information: • Track record in space development (including whether or not spacecraft were developed or project managed, and the number of years of experience in these areas) • The degree of interest in space development · Knowledge related to space development The "Annual Salary Range" item provides information on the range of compensation offered to candidates in the recruitment process.

[0423] Specifically, the item "Annual Salary Range" may include information on the annual salary for the job being advertised.

[0424] The item "Validity Period" contains information about the validity period of the recruitment notice.

[0425] Specifically, the item "Validity Period" may include information about the period during which the recruitment notice is posted.

[0426] The "Expected Compensation Range" item provides compensation information that serves as a guideline for hiring personnel, based on the job description.

[0427] Specifically, the item "Expected Compensation Range" may be information representing the expected evaluation results (including annual salary equivalent information) when the talent evaluation module 2049 evaluates individuals who meet the criteria of items such as "Job Opening" and "Personnel Requirements." By presenting these evaluation results to the recruiting company, it becomes easier for the recruiting company to set compensation when recruiting personnel.

[0428] The "Status" field indicates the status of the job posting from the employer.

[0429] Specifically, the "Status" field may include the following information as a representation of the job posting's status: • Before publication • Currently posted • Listing ended (The listing period has expired, or the target number of hires has been reached, so the listing has been removed.) <8 Operation (Third Embodiment)> Figure 31 shows the process flow for calculating the score of space personnel.

[0430] In step S3121, the personnel evaluation module 2049 of the server 20 evaluates personnel based on at least one of the following: information on personnel's track record of participating in space projects (space development personnel database 218, space project database 215, astronaut database 214, etc.) or information on personnel's track record of developing spacecraft (space development personnel database 218, developed spacecraft database 219, design history database 216, etc.), and updates the user database 211.

[0431] Specifically, in terms of evaluating personnel, the personnel evaluation module 2049 evaluates the compensation (e.g., annual salary) that should be paid to personnel for work related to space projects and updates the user database 211.

[0432] The talent evaluation module 2049 may evaluate talent compensation in the following way:

[0433] (1) Track record of participating in space projects and developing spacecraft. The personnel evaluation module 2049 of server 20 may quantitatively evaluate the personnel's experience, such as the length of time they have participated in space projects (years of experience, etc.) and the scale of the space projects they have participated in, and calculate a compensation score for the personnel.

[0434] The personnel evaluation module 2049 may quantitatively evaluate the personnel's experience, etc., based on the period during which they developed spacecraft, whether or not the development of the spacecraft was successful (whether the intended objectives in the space project were achieved, the degree of stable operation, etc.), and calculate a compensation score for the personnel. For example, the personnel evaluation module 2049 may evaluate personnel based on their track record in developing spacecraft in a simulation environment as described in the above embodiment (for example, the number of spacecraft developed in the simulation, the period of development, the performance of the developed spacecraft, etc.).

[0435] (2) Comparison with the compensation system in organizations conducting space development Server 20 stores information in its memory unit 202 regarding the annual salary of personnel in an organization engaged in space development, based on their performance. In such an organization, for example, a salary system is set up with grades, and the range of applicable grades is generally determined according to the number of years of work experience, and this information is stored in the memory unit 202. The personnel evaluation module 2049 may refer to the information regarding the annual salary of personnel in the organization engaged in space development, compare it with the career history of the personnel being evaluated (such as the number of years of work experience), and evaluate the compensation (e.g., annual salary) that should be given to the personnel being evaluated.

[0436] (3) Evaluation based on information from the businesses where the personnel have been employed. The Talent Assessment Module 2049 may evaluate a talent's compensation based on information about the organization from which the talent previously worked, or information about the organization to which the talent is to work, including potential employers. For example, an organization engaged in space development may be a public institution, an organization that has worked with a public institution, or an organization that has a track record of independently conducting space development. The Talent Assessment Module 2049 may also evaluate a talent's compensation depending on whether the talent is coming from an organization with a certain level of development or operational track record.

[0437] Here, whether an organization has a certain level of development or operational experience may be based on criteria such as the following: • The organization has a certain number of years of experience in space development. • The amount of funding (including public funds) obtained for space development is above a certain level. • The number of publications related to space development, such as papers, that document the results of space development is above a certain level. • The total number of people who have belonged to the organization, and the number of people currently belonging to the organization, are above a certain level. For example, the talent evaluation module 2049 may take into account the fact that an individual belongs to a specific organization that has a certain level of experience in organizational development or operations (i.e., if the organization from which they are transferring is that specific organization) and calculate an evaluation score accordingly (for example, by multiplying their annual salary by a certain coefficient to give them a high evaluation).

[0438] For example, the talent evaluation module 2049 may be designed to give a higher evaluation score when an employee moves from an organization with a certain level of development or operational track record to an organization without such a track record (for example, a newly established company).

[0439] (4) Evaluation based on the position of the personnel in the personnel pool, the space projects in which they participated, etc. The talent evaluation module 2049 may use data on the achievements of each individual in developing spacecraft (data on the achievements of each user, such as the Space Development Talent Database 218) as the population, and evaluate the individual being evaluated according to the position of their achievements. For example, the talent evaluation module 2049 may quantitatively aggregate the degree of achievement for each individual (years of experience, budget size of projects involved, project owner of projects involved, number of papers published, number of awards received, etc.), and identify each individual's standard score, position relative to the median (quartile, etc.) according to the amount of achievement, and evaluate them so that higher scores result in higher evaluations and higher salaries.

[0440] The personnel evaluation module 2049 may evaluate personnel based on at least one of the following: information on the scale of space projects in which the personnel have participated, or information on the project entity of the space projects in which the personnel have participated. Here, a space project in which the personnel have participated may include at least one of the following: experience in developing spacecraft related to the space project, or experience in operating the space project.

[0441] For example, the talent evaluation module 2049 may evaluate talent in such a way that the larger the scale of the space project in which the talent participated (budget size, number of participating businesses, size of businesses, etc.), the higher the evaluation.

[0442] For example, the talent evaluation module 2049 may evaluate talent in a way that gives them a high rating when the entity managing the space project in which they participated is a specific organization (such as an organization with extensive experience in handling space projects).

[0443] (5) Evaluation based on aptitude tests and evaluations from other personnel (references) Server 20 stores information in the user database 211 indicating whether or not a person is suitable for the role. The personnel evaluation module 2049 may evaluate personnel based on this information regarding their suitability. For example, personnel who are suitable may be evaluated more highly than those who are unsuitable.

[0444] Server 20 stores information about personnel evaluations from other individuals in the user database 211. The personnel evaluation module 2049 may determine that a person is suitable for evaluation if their evaluation from other individuals is above a certain level, and may evaluate personnel based on evaluations from other individuals.

[0445] (6) Evaluation based on the influence of personnel Server 20 stores information about a person's personal network (SNS account information) in the user database 211 as information about the influence a person has on other people. The talent evaluation module 2049 may evaluate people based on the information about their personal network. For example, the talent evaluation module 2049 may evaluate people based on information such as the number of impressions when a person posts on SNS and the number of followers a person has, so that people with a higher influence receive a higher evaluation.

[0446] In step S3123, the personnel evaluation module 2049 of the server 20 outputs information on the compensation that should be given to the personnel to the terminal 10 as information based on the evaluation results. For example, the personnel evaluation module 2049 outputs the results of an evaluation of the compensation (which may be in the form of an annual salary) that should be given to personnel for work related to the space project.

[0447] In step S3111, terminal 10 displays to the user the results of an evaluation of the compensation that should be given to personnel for work related to the space project.

[0448] In step S3113, terminal 10 receives a request from the user specifying whether or not the results of the personnel evaluation should be made public.

[0449] In step S3125, the server 20 updates the user database 211 according to the user's specification regarding whether or not the results of the personnel evaluation should be made public.

[0450] Figure 32 shows the process flow for registering the career information of space personnel.

[0451] In step S3221, the talent matching module 2050 of the server 20 outputs an operation screen to the terminal 10 that accepts operations regarding job applications or job postings.

[0452] In step S3211, terminal 10 receives requests from the job seeker user to input their work history and to generate their work history.

[0453] In step S3223, the personnel matching module 2050 of server 20 generates personnel career information based on information stored in various databases (space development personnel database 218, spacecraft development database 219, design history database 216, space project database 215, astronaut database 214, user database 211, etc.) and updates the personnel matching database 223. For example, the personnel matching module 2050 may prompt the server 95 of the large-scale language model service to output career information according to a predetermined format based on user information stored in the above-mentioned various databases (for example, by breaking it down into items such as development achievements and space projects participated in, and defining prompts so that it is within a certain number of characters), thereby causing the server 95 of the large-scale language model service to generate personnel career information, and the server 20 may acquire the generated career information.

[0454] The talent matching module 2050 outputs the generated career information about the user to terminal 10.

[0455] In step S3213, terminal 10 displays the generated personnel's career information and accepts editing requests from the user.

[0456] In step S3227, the server 20 updates the talent matching database 223 according to the user's edits to their resume.

[0457] Figure 33 shows the process flow for accepting registrations of information on desired space personnel.

[0458] In step S3321, the talent matching module 2050 of the server 20 outputs an operation screen to the user terminal 10 of the recruiting party, which accepts the operation to set the desired personnel.

[0459] In step S3311, terminal 10 receives input from the recruiting business user, including information on the personnel they wish to hire, such as personnel requirements and compensation.

[0460] In step S3323, the talent evaluation module 2049 of the server 20 identifies an expected salary range based on the information of the talent to be hired. For example, it identifies a salary range corresponding to the information of the talent to be hired by comparing the requirements information of the talent to be hired with the career information of each user stored in the talent matching database 223 and referring to the salary score information of users with similar careers. The talent matching module 2050 outputs the identified salary range information to the terminal 10.

[0461] In step S3313, terminal 10 receives a specification from the user regarding the timing of the job posting from the job seeker.

[0462] In step S3325, server 20 publishes the job posting information from the recruiting party according to the publication schedule.

[0463] Server 20 may store information in its memory unit 202 regarding the compensation currently offered to candidates for job postings by recruiters, or information regarding their desired compensation, in a talent matching database 223 or the like. Talent matching module 2050 may output information indicating the degree of discrepancy between the compensation currently offered to the candidate being evaluated and the compensation that should be offered to the candidate (compensation score). This provides recruiters with information to help them assess the likelihood of hiring a candidate.

[0464] Figure 34 shows the process flow for matching job seekers and employers in the space industry.

[0465] In step S3411, terminal 10 receives the job-seeking user's setting of their desire to change jobs.

[0466] In step S3423, the talent matching module 2050 of server 20 presents job seeker information to the recruiting organization according to the information of the personnel the recruiting organization desires, accepts offers to job seekers, and updates the talent matching database 223. The talent matching module 2050 outputs a notification that an offer has been made to the terminal 10 of the relevant job seeker's user. For example, the talent matching module 2050 may refer to the talent matching database 223, compare the personnel requirements desired by the recruiting organization with the job seeker's career information, identify job seekers with a high degree of similarity to the personnel requirements, and present the information of the identified job seekers to the recruiting organization's user.

[0467] Server 20 may store information about the compensation currently being paid to a person, or information about their desired compensation, in the personnel matching database 223 or the like in the memory unit 202. Personnel matching module 2050 may output information indicating the degree of discrepancy between the compensation currently being paid to the person being evaluated, or their desired compensation, and the result of evaluating the compensation that should be paid to the person (compensation score). This provides recruiting users with information to assess the likelihood of hiring a person. It also provides job-seeking users with information to assess the likelihood of changing jobs (for example, if there is a discrepancy, the job-seeking user may recognize the possibility of increasing their compensation by changing jobs and may set their preference for changing jobs).

[0468] Thus, the talent matching module 2050 performs the following actions: presents job-seeking users with the results of an evaluation of them (such as a compensation score); accepts the user's request to change jobs on the screen where the evaluation results are presented; and presents job offers from recruiting organizations to the job-seeking user in response to the request to change jobs.

[0469] In step S3413, terminal 10 presents the offer details of the recruiting organization to the job seeker user and accepts the job seeker user's response to the offer.

[0470] Here, the talent matching module 2050 of the server 20 may execute a step on the operation screen displayed on the terminal 10 in which it accepts an operation from the user to specify the organization to which the person is changing jobs. In response to the operation by the user to specify the organization to which the person is changing jobs, the talent matching module 2050 may output the result of evaluating the person's compensation based on at least one of the information of the organization from which the person is changing jobs, or the information of the organization to which the person is changing jobs, including the candidate organization.

[0471] In step S3427, the server 20 updates the talent matching database 223 in response to the user's actions as a job seeker.

[0472] <9. Screen Example (Third Embodiment)> Figure 35 shows an example of a screen that displays scores to space personnel while also accepting requests for job matching.

[0473] The job seeker interface 3500 is a screen that displays the user's score while allowing job seekers to input their work history, apply for jobs, and perform other necessary actions.

[0474] The user information display area 3502 is an area that displays information about users who log in to the services provided by the server 20.

[0475] The compensation score display area 3504 is an area that displays the score (information such as the "Compensation Score" and "Annual Salary Equivalent" items from the user database 211) that has been evaluated by the talent evaluation module 2049 for job seeker users.

[0476] The score details display area 3506 is an area that displays the score details, including the results of the evaluation of the job seeker user, and the reasons for the evaluation (item "Reward Score Evaluation Reason" in the user database 211).

[0477] The score details display area 3506 may display score details in response to user operations. This corresponds to steps S3123 and S3111 in Figure 31.

[0478] The disclosure / non-disclosure designation unit 3508 is an operating component that receives a designation from the job seeker user regarding whether or not to disclose their score to other users.

[0479] The disclosure permission section 3508 indicates, in the illustrated example, that the user has set the score related to the compensation to be private from other users (users on the job posting side and other job seeker users) (item "Compensation Score Disclosure Permission" in the user database 211). This allows job seeker users to prevent their scores from being disclosed to users on the job posting side. This corresponds to steps S3113 and S3125 in Figure 31.

[0480] The career history specification screen 3510 is an operation screen that allows job seekers to specify the career history information they will use when applying for a job.

[0481] The history selection screen 3510 corresponds to steps S3221, S3211, etc. in Figure 32.

[0482] The history designation unit 3512 is an operating component that accepts the user's designation of their history.

[0483] The career designation unit 3512 accepts user input to register career information using free text, images, audio, etc.

[0484] The confirmation operation unit 3514 is an operating component that accepts operations to confirm information about the job seeker user's track record, which is stored in various databases such as the space development personnel database 218.

[0485] The confirmation operation unit 3514 may read and display information stored in various databases in response to user operations.

[0486] The generation operation unit 3516 is an operation member that receives an operation to generate the user's career history for job seekers.

[0487] The generation operation unit 3516 generates user history information in response to user operations, such as by having the server 95 of the large-scale language model service generate it based on information from various databases stored on the server 20.

[0488] The matching selection screen 3518 is an operation screen that accepts requests from job seeker users to match with employers.

[0489] The matching specification screen 3518 corresponds to step S3411, etc., in Figure 34.

[0490] The confirmation operation unit 3520 is an operating component that receives requests from job seeker users to confirm information (such as work history and compensation score) to be disclosed to employers.

[0491] The matching designation unit 3522 is an operating component that receives designations from job seeker users for matching with employers.

[0492] The matching designation unit 3522 registers a record in the personnel matching database 223 in response to user operations.

[0493] Figure 36 shows an example of a screen where employers can specify their desired space personnel.

[0494] The user interface 3524 for employers allows users of the job posting business to register desired personnel, view candidate profiles, and perform other related tasks.

[0495] The user interface 3524 for job seekers corresponds to Figure 33.

[0496] The user information display area 3526 is an area that displays information about the recruiting user who logs in to the service provided by server 20.

[0497] The desired candidate registration screen 3528 is an operation screen that allows users from the job-seeking side to register their desired candidates.

[0498] The requirements specification unit 3530 is an operating member that receives the specification of the requirements for the desired personnel.

[0499] The predicted score display area 3532 is the area that displays the expected compensation score for the requirements of the desired personnel.

[0500] The predicted score display area 3532 corresponds to step S3323 in Figure 33, etc.

[0501] The registration operation unit 3534 is an operating component that accepts operations to register the requirements of the desired personnel.

[0502] The registration operation unit 3534 registers a record in the desired personnel database 224 in response to the user's operation.

[0503] The candidate display screen 3536 is an operation screen that displays candidates who have applied for a position.

[0504] The recruitment requirements viewing operation unit 3538 is an operating component that accepts requests to view the details of the recruitment.

[0505] The predicted score display area 3540 is an area that displays the expected compensation score based on the personnel requirements related to the job posting.

[0506] The personnel verification operation unit 3542 is an operating component that receives operations to view information on candidates for personnel in response to recruitment (applicants and personnel who meet the requirements for personnel in the recruitment).

[0507] The personnel verification operation unit 3542, in response to user operations, refers to the personnel matching database 223 and displays information on applicants and candidates who fit the recruitment requirements.

[0508] The past recruitment viewing screen 3544 is a screen for viewing information about recruitment postings whose posting period has ended.

[0509] The past recruitment viewing operation unit 3546 is an operating component that accepts requests to view details of recruitment information that has been posted in the past and is no longer available.

[0510] The predicted score display area 3548 is an area that displays the expected compensation score based on the personnel requirements for job postings that have been published in the past.

[0511] The past application confirmation operation unit 3550 is an operation component that accepts operations to view information on candidates for personnel (personnel who applied, personnel who meet the requirements for personnel related to the recruitment) for job postings that were posted in the past.

[0512] Figure 37 shows an example of a screen display when a match is made between a job seeker and a company offering space-related services.

[0513] The offer display screen 3552 is an operation screen that displays offers from employers to job-seeking users.

[0514] The offer display screen 3552 corresponds to step S3423 in Figure 34, etc.

[0515] The recruitment requirements viewing operation unit 3554 is an operating component that accepts operations to view the details of the recruitment content related to the offer.

[0516] The application operation unit 3556 is an operating component that receives the operation to apply for an offer.

[0517] The application operation unit 3556 corresponds to step S3413 in Figure 34, etc.

[0518] The job posting viewing screen 3558 is the user interface where job seekers can view the job postings they have searched for.

[0519] The recruitment details display area 3560 is the area that displays the details of the recruitment.

[0520] The predicted score display area 3562 is an area that displays the expected compensation score if a job seeker user applies and is hired.

[0521] The predicted score display area 3562 displays, for example, the results of a talent evaluation module 2049's assessment of the expected compensation score if the employee were to change jobs, based on information from the organization the employee currently belongs to and information from potential employers.

[0522] The search operation unit 3564 is an operating component that receives requests from employers to search for other job postings.

[0523] The search operation unit 3564 searches the job postings stored in the desired personnel database 224 in response to user operations. The personnel matching module 2050 may also search for job postings that include the requirements of personnel similar to the job seeker user's career information and present them to the job seeker user.

[0524] The application operation unit 3566 is an operating component that receives the operation to apply for the recruitment.

[0525] The application operation unit 3566 updates the talent matching database 223 in response to user operations.

[0526] <Fourth Embodiment> The fourth embodiment will now be described. The fourth embodiment addresses the challenge in the space industry of finding a business partner capable of performing tasks such as design, material processing, and control software development (for example, a business partner capable of designing, manufacturing, and processing an object to create the intended object). In this way, the aim is to make it easier for the space industry to find business partners to whom tasks related to space projects can be commissioned, thereby further promoting space projects.

[0527] Specifically, for requests related to space projects, a score will be calculated for each company or individual that can undertake the work based on their track record in space development. Candidates will then be presented according to their scores, making it easier to find suitable contractors. For example, by making it easier to verify the track record of potential contractors in space development, the system will facilitate the selection process for potential contractors.

[0528] Here, when considering potential contractors for space development, it is also possible to consider their experience in developing simulations using the above-mentioned simulation processing module 2045 when selecting them as candidates for outsourcing work. This allows for the selection of potential contractors based on their experience in designing simulations, even if a space development company has little or no experience in conducting demonstration tests or participating in actual space project operations, thereby expanding the range of business partners. Furthermore, for companies entering space development, even if they have not yet accumulated experience in spacecraft demonstration tests and operations in space projects, they can still be selected as potential contractors, further encouraging companies to enter the space development field.

[0529] <10 Data Structure (Fourth Embodiment)> Figure 38 shows the data structure of the request details registration database 225. The request details registration database 225 includes the following fields: "Request ID", "Requester ID", "Job Request Category", "Job Request Details", "Status", "Job Responsible Person ID", "Request Registration Date", "Matching Date", "Request Data", "Transaction Terms", "Transaction Evaluation", and "Work Completion Date".

[0530] The "Request ID" field is information that identifies each request for services related to the space project.

[0531] The "Client ID" field is information that identifies the client requesting the service.

[0532] The item "Requester ID" may be associated with the item "Business ID" or the item "User ID" in the user database 211.

[0533] The item "Service Request Category" contains information about the type of service request.

[0534] The item "Service Request Category" may include the following as types of service requests: • Types of work content, such as design, manufacturing, processing, and software development. • Hardware that is subject to structure or control, such as artificial satellites, robots for spacecraft, probes, and spacecraft. The item "Details of the work request" contains information about the details of the work request.

[0535] More specifically, the item "Service Request Details" contains information about the request entered by the requester.

[0536] The "Status" field contains information about the status of the work request.

[0537] The "Status" field may include the following as a representation of the status of the work request: • Registration of the request (before disclosing the request details to potential service providers) • Public disclosure of the request (the details of the request are disclosed to potential contractors). • Request successful (matching between the requester and the service provider is completed. This includes situations where negotiations regarding transaction terms, etc., are ongoing.) • Transaction completed (the requested work has been performed) The item "Task Responsible Person ID" is information that identifies the party to whom the task was requested.

[0538] More specifically, the item "Task Responsible Person ID" is information that identifies the organization to which the task is requested, or information that identifies the individual (or team) to whom the task is requested.

[0539] The "Request Registration Date" field indicates the timing of the request registration.

[0540] The item "Matching Completion Date" is information about the timing when the requester and the service provider were matched in response to the request.

[0541] More specifically, the item "Matching Completion Date" refers to the time when the recipient responds to the request, or the time when the requester confirms the recipient, etc.

[0542] The item "Request Data" contains information about data files related to the request.

[0543] The item "Request Data" may include the following as data files related to the request: • Data file of specifications related to the design request • Data files of design specifications related to manufacturing and processing requests • Data file of specifications related to software development requests The item "Terms of Transaction" contains information about the terms and conditions of the transaction related to the request.

[0544] More specifically, the item "Terms of Transaction" contains information about the fees, deadlines, and other conditions related to the request.

[0545] The item "Transaction Evaluation" contains information about the evaluation of the transaction related to the request.

[0546] More specifically, the item "Transaction Evaluation" is information resulting from evaluations of the transaction received from at least one of the clients or the client company upon completion of the transaction.

[0547] The item "Completion Date" indicates the timing when the requested work was completed.

[0548] More specifically, the "Completion Date" field indicates the time when the client registered that the work had been completed.

[0549] <11 Operation (Fourth Embodiment)> Figure 39 shows the process flow for matching business requests by extracting potential service providers based on the requester's registration of the request details and accepting the requester's specifications.

[0550] In step S3921, the server 20's task request matching module 2051 presents terminal 10 with an operation screen for entering the details of a task request regarding a space project.

[0551] Server 20 records information about entities that conduct space development (individual users, organizations, etc., as shown in the user database 211, space development personnel database 218, etc.) in its memory unit 202, associating it with information about the entities' achievements in space development (design history database 216, space development personnel database 218, developed spacecraft database 219, etc.).

[0552] In step S3911, terminal 10 receives an input from the user for a task request regarding the space project. Terminal 10 then sends the information of the task request received to server 20.

[0553] In step S3923, the business request matching module 2051 of server 20 receives information on the details of the business request from terminal 10 and updates the request registration database 225. The business request matching module 2051 refers to information on the space development track record of each business operator and individual (design history database 216, space development personnel database 218, developed spacecraft database 219, etc.) and extracts businesses and individuals corresponding to the request as candidates for the entity that will respond to the request. For example, based on the information of the request details below, the business request matching module 2051 obtains keywords for extracting the entity that will respond to the request (for example, it performs processing to extract important keywords using a language model (such as server 95 of the large-scale language model service)) and performs processing such as vectorizing the text of the request details. • The wording of the category related to the content of the work request (item 225 in the request content registration database, "Work Request Category") • The wording of the work request (item "Work Request Details" in the Request Details Registration Database 225) • Data related to the work request, such as design documents and specifications (item "Request Data" in Request Details Registration Database 225) Furthermore, the business request matching module 2051, in order to match a requester with a service provider, refers to the requester's information (the "Requester ID" item in the request details registration database 225), identifies information on space projects in which the requester has participated (items such as "Project Participants" and "Purpose / Goals" in the space project database 215, and items such as "Participating Projects," "Development Results," "Operational Results," and "Presentation Results" in the space development personnel database 218), and performs processing such as extracting keywords related to the requester.

[0554] The business request matching module 2051 performs the same processing as described above, such as extracting important keywords from potential service providers and personnel.

[0555] The Business Request Matching Module 2051 identifies service providers that match the request content. Based on the requester's information, keywords extracted from the request content, and calculated vectors, it compares these with keywords and vectors extracted from potential service providers to calculate a score indicating the degree of matching for each candidate. The Business Request Matching Module 2051 then sets a priority order for presenting service provider candidates based on their scores (prioritizing those with higher scores).

[0556] Furthermore, the business request matching module 2051 may also obtain the results of extracting candidate clients from the server 95 of the large-scale language model service by providing the server 95 with the above-mentioned client information, client request details, and candidate client track record, while also providing prompts to identify candidate clients with similar track records to the client information and client request details (these prompts may include instructions to output information about the track record that formed the basis for extracting candidate clients (for example, a track record of developing spacecraft, a track record of participating in space projects)). In this way, candidate clients may be extracted based on the results of searching for candidate clients' track records by emphasizing the information about the request details (for example, emphasizing keywords included in the request details), or candidate clients may be extracted by considering the client's past track record (space projects participated in, spacecraft developed, etc.).

[0557] Furthermore, the business request matching module 2051 may identify potential service providers capable of handling a given category based on the category related to the request (the "Business Request Category" item in the request registration database 225). For example, if the category includes information indicating the nature of the work, such as "design," the module may identify potential service providers capable of performing design work. If the category includes information indicating the type of hardware, such as "artificial satellite," the module may identify potential service providers capable of developing that hardware. The business request matching module 2051 may also match potential service providers to the request by maintaining information about the types of work each potential service provider can handle as a profile, etc. For example, the server 20 may manage potential service providers by assigning tags corresponding to the above categories. These tags may be set by the potential service providers themselves, or the server 20 may assign tags based on the potential service providers' development track record, or the requesting party may set tags in their evaluation of the service providers.

[0558] As described above, the Task Request Matching Module 2051 acquires information on the details of requests for services related to space projects. Based on the acquired request information and the information on each entity's space development track record stored in the memory unit, the Task Request Matching Module 2051 extracts entities that have the necessary experience to handle the requested tasks.

[0559] More specifically, the design history database 216, the space development personnel database 218, and the developed spacecraft database 219, among others, include information on the space development achievements of personnel belonging to the entity as part of the entity's space development track record. The task request matching module 2051 extracts personnel who have experience handling tasks related to the request by referring to each of the above databases. The task request matching module 2051 may present the extracted entities to the user making the request by presenting either the personnel or the entity to which the personnel belong.

[0560] Furthermore, the storage unit 202 of the server 20 is configured to store information related to space projects (such as the space project database 215). The storage unit 202 also stores information on personnel's achievements in space development (space development personnel database 218), including information on space projects in which personnel have participated (items such as "Participating Projects" in the space development personnel database 218, and items such as "Project ID" and "Developer User ID" in the spacecraft development database 219). The work request matching module 2051 may also identify information on space projects related to the work requested by referring to each database in the storage unit 202, and extract personnel who have participated in the identified space projects.

[0561] The storage unit 202 of server 20 is configured to store information related to spacecraft (design history database 216, developed spacecraft database 219, etc.). The storage unit 202 also stores information on personnel's achievements in space development, including information on the achievements of spacecraft developed by personnel (design history database 216, developed spacecraft database 219, etc.). The task request matching module 2051 may also refer to each database in the storage unit 202 to identify information on spacecraft related to the task requested and extract personnel who developed the identified spacecraft.

[0562] The simulation processing module 2045 of server 20 provides the user with a process that simulates the operation of spacecraft design data in a space environment and responds with the simulation results. Server 20 stores information on the experience of personnel in space development, specifically information on the experience of developing spacecraft through simulation (design history database 216), in the memory unit 202. The task request matching module 2051 may also extract personnel who have developed spacecraft related to the task requested by referring to the experience of developing spacecraft through simulation. In this way, by extracting personnel with experience in developing spacecraft under a simulation environment, or organizations to which such personnel belong, the process of requesting tasks in space development can be made even smoother.

[0563] Server 20 stores information on the performance of spacecraft developed by personnel (Developed Spacecraft Database 219) in its memory unit 202, and may include at least one of the following: the performance of spacecraft that have undergone demonstration tests (item "Demonstration Test Performance" in the Development Spacecraft Database 219), or the performance of spacecraft that have been operated in space projects (item "Utilization Performance Projects" in the Development Spacecraft Database 219). The task request matching module 2051 identifies information on spacecraft related to the task requested, and may identify spacecraft based on at least one of the following: the performance of spacecraft that have undergone demonstration tests, or the performance of spacecraft that have been operated in space projects. In this way, by extracting personnel with a track record of developing spacecraft that have undergone demonstration tests and operational experience, or organizations to which such personnel belong, the task request process in space development can be made even smoother. Furthermore, priority may be given to extracting personnel who have developed spacecraft with a large track record of demonstration tests and operational experience.

[0564] The memory unit 202 may also store information about personnel, specifically a score that evaluates each individual based on their achievements in space development (such as the "Evaluation Score" item in the user database 211). The task request matching module 2051 may extract personnel based on their scores. For example, personnel with high scores may be prioritized for extraction.

[0565] As described above, the memory unit 202 is configured to store at least one of either information relating to space projects or information relating to spacecraft. The memory unit 202 may also include, as information on the entity's achievements in space development, at least one of either the entity's achievements in developing spacecraft or the entity's achievements in space projects in which it participated. The task request matching module 2051 may refer to these databases to identify information on spacecraft or space projects related to the task requested, and extract the entities that developed the identified spacecraft or participated in the space project.

[0566] As described above, the server 20, through the simulation processing module 2045, provides the entity with a process to perform a simulation of what the spacecraft design data would look like when operated in a space environment and to respond with the simulation results. The memory unit 202 stores information on the entity's achievements in space development, specifically information on the entity's achievements in spacecraft development through simulation (design history database 216). The task request matching module 2051 may also extract entities that have developed spacecraft related to the task requested by referring to the achievements in spacecraft development through simulation stored in the design history database 216.

[0567] As described above, the server 20 stores information on the performance of spacecraft developed by the entity in its memory unit 202 (development spacecraft database 219), and may include at least one of the following: the spacecraft has undergone demonstration testing, or the spacecraft has been operated in a space project. The task request matching module 2051 identifies information on spacecraft related to the task requested, and may identify spacecraft based on at least one of the following: the spacecraft has undergone demonstration testing, or the spacecraft has been operated in a space project. The task request matching module 2051 may also prioritize spacecraft that have undergone demonstration testing or have been operated in a space project.

[0568] Server 20 stores information about space projects in its memory unit 202, including information about entities that participated in space projects and information about the funds acquired by those projects (space project database 215, financial support history database 221). The business request matching module 2051 may refer to each database in the memory unit 202 to identify information about space projects related to the business request based on the information about the funds acquired by those space projects, and extract information about the entities that participated in the identified space projects. For example, the business request matching module 2051 may prioritize space projects that have acquired a relatively large amount of funding, and may extract information about the entities that participated in space projects that have acquired a large amount of funding.

[0569] The business request matching module 2051 may acquire information on the requested services, including at least one of the following: design, manufacture, or processing of spacecraft related to a space project, or development of software to control the spacecraft. Here, the business request matching module 2051 may also include data related to the requested services for the space project (e.g., specifications, design documents, etc.) to be presented to those receiving the request, such as designers, manufacturers, processors, and software developers (request registration database 225). The business request matching module 2051 may also refer to the request registration database 225 and extract entities with experience corresponding to the requested services based on the request data.

[0570] In step S3925, the business request matching module 2051 of the server 20 presents the extracted candidate entities to the requester user's terminal 10.

[0571] Here, the business request matching module 2051 may present the extracted entities and information on their space development track record to the user making the request. The business request matching module 2051 may also present the extracted entities, along with information on their space development track record, specifically information on track record relevant to the requested tasks. This makes it even easier for the user making the request to select a suitable candidate for their project.

[0572] In step S3913, terminal 10 presents the extracted candidate entities and accepts an operation from the user to specify the recipient.

[0573] In step S3927, the business request matching module 2051 of server 20 receives information about the recipient specified by the requesting user and updates the request details registration database 225. The business request matching module 2051 notifies the specified recipient that a request has been made. The business request matching module 2051 receives a specification from the recipient indicating whether or not they will accept the request, updates the request details registration database 225, and notifies the requesting user of the result specified by the recipient.

[0574] As described above, the business request matching module 2051 accepts operations from the requesting user to specify a candidate entity to which the request should be made, and to request the specified entity to perform the work related to the request. The business request matching module 2051 stores in the request content registration database 225 that a business request has been received from the user, associating it with the information of the specified entity.

[0575] The business request matching module 2051 receives information on the transaction price related to business requests from the requesting user. The business request matching module 2051 stores the transaction price information in the request content registration database 225 in association with the acceptance of the request. The business request matching module 2051 may also refer to the transaction price information in the request content registration database 225 and present the user with information on the extracted entity, along with information on the transaction price that can serve as a reference when requesting business. For example, the business request matching module 2051 identifies past requests similar to the request in question. The business request matching module 2051 extracts the business content, keywords included in the request, etc., related to the request in question to identify similar past requests. Based on the transaction price information of the identified similar past requests, the business request matching module 2051 may also present the average, median, etc. of the transaction price as a reference transaction price. This makes it even easier for the requesting party and the service provider to set the transaction price.

[0576] Furthermore, the business request matching module 2051 may refer to the request content registration database 225 to obtain information on past transaction prices for each candidate service provider and display reference transaction price information for each candidate service provider. For example, by displaying the transaction price history, average transaction price, median transaction price, etc. for past requests, it becomes even easier to compare the actual transaction prices of each service provider and to consider and evaluate service providers.

[0577] In step S3915, if there is a party willing to accept the request, terminal 10 displays that information and accepts the requesting user to specify the transaction terms (transaction price, transaction quantity, deadline for the request, etc.).

[0578] In step S3929, the business request matching module 2051 of the server 20 receives the transaction conditions specified by the requesting user and updates the request details registration database 225. The business request matching module 2051 presents the requesting party with information on the requesting party's transaction conditions, receives the requesting party's specification of the transaction conditions and whether or not to accept the request based on those conditions, and updates the request details registration database 225.

[0579] Figure 40 shows the process flow for matching business requests by having the requester register the details of the request, and the entity receiving the request specifying the details of the request.

[0580] In step S4025, the business request matching module 2051 of the server 20 presents the information of the requester and the information of the request from the request content registration database 225 to the extracted candidate entities, one or more of them.

[0581] In step S4027, the business request matching module 2051 of server 20 receives a designation from each of the extracted candidate entities whether or not to respond to the request, and updates the request content registration database 225. The business request matching module 2051 then presents the information of the entities that have indicated they will respond to the request to the user who made the request.

[0582] In step S4013, the requesting user's terminal 10 presents the entities that have designated themselves as willing to respond to the request, and accepts an operation from the user to confirm which of these entities will be the recipient of the request.

[0583] In step S4029, the business request matching module 2051 of server 20 receives information about the recipient specified by the requesting user and updates the request content registration database 225. The business request matching module 2051 notifies the recipient specified by the requesting user that the requester has confirmed the request.

[0584] This allows the system to present the client with information on potential service providers who can fulfill their request, enabling the client to select a provider and thus facilitate matching between the client and the service provider.

[0585] <12 Screen example (Fourth embodiment)> Figure 41 shows an example of a screen where a client registers the details of their request for services.

[0586] The request input screen 4100 is an operation screen that receives requests from users requesting space development work.

[0587] The request input operation screen 4100 corresponds to the processes in steps S3921, S3911, etc., in Figure 39.

[0588] The account display area 4102 is the area that displays the user's account information.

[0589] The request details display area 4104 is an area that displays information about the request details entered by the requesting user.

[0590] The request category designation unit 4106 is an operating component that accepts the designation of the category of the requested work.

[0591] More specifically, the request category designation unit 4106 is an operating component that accepts the designation of a pre-prepared category. The request category designation unit 4106 may also accept the designation of information managed in the "Business Request Category" item of the request content registration database 225 from the user.

[0592] The request content specification unit 4108 is an operating component that receives the specification of the details of the work request.

[0593] More specifically, the request content specification unit 4108 is an operating component that receives input of the request content from the requesting user in free text format.

[0594] The request data acquisition unit 4110 is an operating component that accepts operations to acquire data related to the content of a business request.

[0595] More specifically, the request data acquisition unit 4110 is an operating component that accepts the upload of data managed in the "Request Data" item of the request content registration database 225.

[0596] The similar request display area 4112 is an area that displays past requests that are similar to the entered request content.

[0597] In the illustrated example, the similar request display area 4112 displays past requests that are similar to the entered request content, and may display the number of requests (which may be the number of requests over a certain aggregation period) and the number of successful cases (such as cases that have recently started transactions or cases that have been completed). The business request matching module 2051 refers to the request content registration database 225 and identifies similar past requests, then displays the aggregated results as follows: • Past requests that fall under the same or similar categories of work. For example, you can pre-group similar categories together. • Past requests with the same or similar content. For example, the degree of similarity of the content of the "Business Request Details" item in the request details registration database 225 may be determined by a language model, or important keywords may be extracted and the degree of keyword matching may be determined. • Past requests with similar content to the attached request data. The server 20 may, upon receiving input of request details in each item of the request details display area 4104, extract similar cases to the request details and display them in the similar request display area 4112.

[0598] The request transmission operation unit 4114 is an operation component that accepts the operation to send the request content to candidate recipients based on the input request content. In this way, by displaying the request content in the request content display area 4104 and displaying past case results in the similar request display area 4112, it becomes even easier for the user to determine whether or not there are recipients who will respond to the request they have entered. For example, if there seems to be little experience with this type of request (few cases, no successful cases, etc.), the user can decide to revise the request content.

[0599] The request transmission operation unit 4114 corresponds to the process shown in step S3911 and other steps in Figure 39.

[0600] Figure 42 shows an example of an operation screen that allows the requester to specify candidate service providers extracted according to the content of the request.

[0601] The candidate recipient display area 4116 is an area that displays candidate recipients extracted according to the content of the request.

[0602] The candidate request display area 4116 corresponds to the processes in steps S3925, S3913, etc. in Figure 39.

[0603] The recipient designation unit 4118 is an operating component that accepts the designation of the recipient to whom the request content will be sent from among the extracted candidate recipients.

[0604] In the illustrated example, the request destination designation unit 4118 displays multiple candidate request destinations, which may be arranged according to priority. Prioritizing request destinations may prioritize those with a relatively large track record of handling tasks related to the entered request (this may include experience in the space development simulation environment provided by server 20). Furthermore, as shown in the illustration, the candidate request destination may display information on their development and other related experience (such as information on space projects related to development and operation similar to the request, or information on spacecraft development experience), allowing the user to view detailed information in response to user actions.

[0605] Furthermore, if the user specifies a candidate for the request (a business or individual), information about the specified candidate (such as experience in developing spacecraft or participating in space projects) may be displayed.

[0606] The transaction terms specification unit 4120 is an operating component that accepts the specification of transaction terms for a transaction with the client.

[0607] The request destination confirmation operation unit 4122 is an operation component that accepts the operation to send the request details to the request destination specified by the requesting user from among the candidate request destinations.

[0608] The request destination confirmation operation unit 4122 corresponds to the process shown in step S3913 in Figure 39.

[0609] Figure 43 shows an example of an operation screen that allows a requester to specify transaction terms to a party capable of fulfilling the request.

[0610] The trading partner display area 4124 is an area that displays information about the requesting party that has responded by agreeing to accept the request.

[0611] The trading partner display area 4124 corresponds to the processes in steps S3927, S3915, etc., in Figure 39.

[0612] The request recipient information display area 4126 is an area that displays information about request recipients who can fulfill the request.

[0613] In the illustrated example, the client information display area 4126 displays the name of the candidate client and information about the estimated work period. For example, when a candidate client specifies that they can accept the request (step S3927 in Figure 39), the system may accept the specification of the estimated work period from the candidate client and update the request details registration database 225. Alternatively, the business request matching module 2051 may refer to the request details registration database 225 and, based on the candidate client's track record of accepting requests and completing work, identify an estimated work period (for example, the average period from the successful matching of similar requests in the past to the completion date) and display the identified estimated work period. Furthermore, the client information display area 4126 may display detailed information about the candidate client (for example, information on space projects they have participated in, information on spacecraft they have developed, etc.) in response to user operations. This makes it even easier for the requesting user to set transaction conditions with the client.

[0614] The transaction terms specification unit 4128 is an operating member that accepts the specification of transaction terms to be presented to the client.

[0615] In the illustrated example, the transaction terms specification unit 4128 receives the transaction terms from the requesting user, including the unit price, quantity, and desired delivery date. This corresponds to the processes in steps S3915 and S3929 of Figure 39.

[0616] The condition transmission operation unit 4130 is an operating component that receives an operation to transmit transaction conditions to the presented requesting party.

[0617] In the illustrated example, the condition transmission operation unit 4130 accepts the specification of transaction conditions from the requesting user, but it may also accept the specification of transaction conditions from the requesting user and present them to the requesting user. This would further encourage negotiation of transaction conditions.

[0618] Figure 44 shows an example of a screen display where potential service providers search for requests registered by the client and apply to accept the request.

[0619] The request search operation screen 4132 is an operation screen that accepts the operation of searching for requests for services related to space projects among the candidate request recipients.

[0620] In the illustrated example, the request search operation screen 4132 shows an example where a candidate user to whom a request is made searches for a request and then decides whether or not to accept the request.

[0621] In addition, in the search results display area 4146 described later, a list of requests may be displayed without the user of the potential recipient performing a search operation.

[0622] In this case, the business request matching module 2051 may identify requests that the candidate can accept based on their track record (e.g., a high degree of match between the request content and the candidate's track record), and display the identified requests in order of registration, based on criteria such as the degree of match between the request content and the candidate's track record. This will save the candidate a lot of trouble searching for requests, thus further promoting matching between clients and service providers.

[0623] The request search operation screen 4132 corresponds to the process shown in step S4025 of Figure 40.

[0624] Account display area 4134 is the area that displays the account information of the user to whom the request was made.

[0625] Search criteria display area 4136 is the area that displays the search results for requests for services related to space projects.

[0626] In the illustrated example, the search condition display area 4136 is used by the user of the prospective requesting party to specify various search conditions. However, the business request matching module 2051 may also set the search conditions such as the search category specification unit 4138, the search term specification unit 4140, and the data availability specification unit 4142, which will be described later, by referring to the prospective requesting party's track record (information on space projects participated in, spacecraft developed, etc., information from the request content registration database 225, etc.) and setting a score for the request content that it can handle.

[0627] For example, if the number of requests for work in the "design" category exceeds a certain number, the search category specification unit 4138 may be set to "design" (allowing changes) without user intervention from the prospective client. Alternatively, the search category specification unit 4138 may be set to a category ("design") without user intervention from the prospective client business or individual profile (for example, if their profile states that they can handle "design").

[0628] This reduces the effort required to search for potential service providers, further facilitating matching between clients and potential service providers.

[0629] The search category specification unit 4138 is an operating member that accepts the specification of the category of the request to be searched.

[0630] The search term specification unit 4140 is an operating component that accepts the specification of free text to be searched for in the request content to be searched.

[0631] The data presence / absence specification unit 4142 is an operating component that accepts the specification of whether or not data such as design drawings are attached when searching for a request from the client.

[0632] In the illustrated example, the data presence / absence specification unit 4142 accepts the specification of whether or not data related to the request is attached, but it may also accept the specification of the data type (specification document, design document, etc.) as a search condition.

[0633] The request search operation unit 4144 is an operating component that accepts operations to search for request content based on the entered search conditions.

[0634] The search results display area 4146 is the area that displays the results of searching for requests according to the search criteria.

[0635] In the illustrated example, the search results display area 4146 prioritizes displaying requests from the client that are extracted according to the search criteria shown in the search criteria display area 4136, prioritizing those that can be handled based on the experience of the candidate service provider (i.e., those with a high degree of match between the request content and the experience of the candidate service provider).

[0636] The request details display area 4148 is the area that displays the details of the request from the requester.

[0637] In the illustrated example, the request details display area 4148 displays the requester's information and the details of the request, while also indicating that potential recipient users can select each request and accept it.

[0638] The client verification operation unit 4150 is an operating component that accepts operations to verify the client's track record.

[0639] In the illustrated example, the requester verification operation unit 4150 verifies the requester's track record by displaying information such as the requester's space development track record, request history, and payment history for requests. This provides potential requesting users with information to help them decide whether or not to accept the request, thereby further promoting matching.

[0640] The business confirmation operation unit 4152 is an operating component that accepts operations to confirm ongoing tasks at the candidate service provider.

[0641] In the illustrated example, the task confirmation operation unit 4152, in response to user operations, refers to the request content registration database 225 and presents a list of ongoing tasks (for example, tasks for which a request has been accepted but has not yet reached the transaction completion status) to the prospective user. This makes it easier for the prospective user to consider an estimated timeframe for completing the work for the request. It also makes it easier for them to decide whether or not to accept the request based on the workload (whether they can accept the request if the workload is small, or whether they should decline the request if the workload is excessive). As a result, the accuracy of the progress of requests can be further increased.

[0642] <Variation>

[0643] (1) An example of providing a simulation function for the space environment and determining whether it meets the constraints. In the above description of the embodiment, an example was described in which the registration of device design data is received from the user, and whether the constraints are met is determined based on the information of constraints such as gravity shown in the constraint database 212. For example, whether the constraints are met may be determined as follows. Electronic components such as power supplies used in a vacuum cannot be cooled by air, so it is necessary to efficiently transfer heat from the circuit board to the chassis, etc. In the space development simulation environment provided by Server 20, heat generation from electronic components is simulated, and heat transfer to each part such as the device chassis and insulating materials is simulated assuming that there is no cooling by air. As a result, it may be possible to simulate the possibility of insufficient heat dissipation materials or that the temperature of a particular electronic component becomes too high and it does not function properly. • In outer space, temperature fluctuations are greater than on Earth depending on the direction the equipment is facing the sun. The system simulates whether a device is designed to withstand such temperature fluctuations. For example, by comparing the operating temperature of the device with the temperature changes in outer space, the system may simulate whether the device will not function properly or will fail. In this case, server 20 may search for products that can withstand temperature changes from the product manufacturer's server 96, etc., and present them to the user. Also, metals may break due to repeated expansion and contraction caused by temperature changes. Server 20 may simulate, for example, the possibility that the microstrip lines of an antenna may break due to repeated expansion and contraction caused by temperature changes, and present the results to the user.

[0644] (2) Mechanisms to encourage investment and lending In the above description of the embodiments, as an example of encouraging investment or financing, it was explained that, if the space project is to be implemented commercially, granting the right to receive a share of the profits as a perk for investment or financing, and making that right tradable and available for exchange, would be an example of such encouragement.

[0645] Here, the following may be offered as incentives for investment or loans: • The rewards should be deliverables appropriate to the nature of the space project. For example, if a space project involves exploration and brings back materials collected during the exploration to Earth, the reward could be the acquisition of those collected materials. • Investing in or financing a space project may be rewarded with the inclusion of one's name or other indication of involvement in the space project. • In exchange for investing in or financing a space project, you could offer perks such as priority access to information about the project's progress (e.g., receiving regular project updates, or being able to watch live streams of the project's progress). • By investing in or financing a space project, investors may be able to participate in events related to the project (such as those featuring developers and astronauts), and depending on the amount of investment or financing, they may be given perks such as a higher chance of participation or priority seating at events. Furthermore, as described in the third embodiment, the score calculation module 2047 may evaluate the space project in which the personnel participate based on the results of the personnel evaluation module 2049's evaluation of the personnel. For example, the score calculation module 2047 may evaluate the likelihood of success of the space project based on the evaluation results of the personnel evaluation module 2049 for the personnel participating in the space project (for example, by summing up or averaging the compensation scores for each person in the space project). Similarly, the evaluation of a spacecraft related to a space project may be based on the evaluation results of the personnel evaluation module 2049 for the personnel involved in the development of the spacecraft (for example, by summing up or averaging the compensation scores for these personnel). Based on the evaluation of the spacecraft, the likelihood of success of the space project using the spacecraft may be evaluated.

[0646] Furthermore, the server 20 may evaluate space development operators based on the evaluation results of the personnel evaluation module 2049 for personnel belonging to said operators.

[0647] As described above, the results of the personnel evaluation module 2049 can be used to identify scores for the space project itself and the businesses participating in the space project, and these scores can be presented to investors, etc., to receive loans or investments.

[0648] (3) Mechanisms to encourage job changes and recruitment of personnel In the above description of the embodiment, an example was described in which the talent evaluation module 2049 evaluates a person based on information about the employers from which the person has worked. For example, it was explained that the talent evaluation module 2049 may evaluate the person's compensation based on at least one of the following: information about the organization from which the person previously worked, or information about the organization to which the person is applying, including potential employers.

[0649] Here, as organizational information, as described in the second embodiment, the amount of investment or loans received (or the amount of insurance payments made in space projects) may be reflected in the evaluation of personnel while they are employed by the organization. For example, the larger the amount of investment or loans an organization receives, the higher the evaluation of personnel who have been employed by that organization may be.

[0650] Furthermore, when the personnel evaluation module 2049 evaluates personnel based on the scale of a space project and their participation in the said space project, it may also evaluate personnel in accordance with the amount of investment or loans received by the space project (or the amount of insurance payments made to the space project). For example, personnel may be valued more highly the larger the amount of investment or loans received.

[0651] <Other> A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0652] Furthermore, by distributing all or part of each hardware configuration across multiple computers and connecting them to each other via a network, a computer can be virtually realized. Thus, the concept of a computer includes not only computers housed in a single enclosure or case, but also virtualized computer systems.

[0653] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.

[0654] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, and Java (registered trademark).

[0655] Furthermore, the program code for the software that implements the functions of the embodiment may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the computer's processor may read and execute the program code stored in the storage means or storage medium.

[0656] The functions realized by the components described herein may be implemented in a circuit or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPUs (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to realize the functions described herein. A processor is considered to be a circuit or processing circuitry, including transistors and other circuits. A processor may be a programmed processor that executes a program stored in memory.

[0657] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.

[0658] If the hardware is a processor that is considered to be a type of circuitry, then the circuitry, means, or unit is a combination of hardware and software used to constitute the hardware and / or processor.

[0659] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0660] (Note (First Embodiment)) The details described in each of the above embodiments are noted below.

[0661] (Note 1) A program for operating a computer comprising a computer processor and memory, configured to store parameters of each item affecting the control of equipment in the space environment in the memory, the program causing the computer processor to perform the steps of: acquiring design data related to the design of a device; calculating a simulation of the device based on the parameters stored in the memory when the device based on the received design data is operated in the space environment; and presenting the results of the simulation.

[0662] (Note 2) The program described in Appendix 1, wherein the memory unit includes, as parameters for each item, at least one of the following parameters: gravity parameter, temperature parameter, communication parameter, power parameter, air parameter, and radiation parameter.

[0663] (Note 3) A program as described in either Appendix 1 or 2, in which the acquisition step includes, as a device, at least one of the following: devices for use inside a space colony (including drones for use inside a space colony), devices for use outside a space colony, satellites, or exploration equipment.

[0664] (Note 4) A program as described in any of the appendices 1 to 3, which, in the acquisition step, includes at least one of the following as design data: data defining the device specifications or data of the device design drawings.

[0665] (Note 5) A program described in any of the appendices 1 to 4, which simulates the operation of devices in a space environment during the calculation step, and calculates the operation of each device by simulating multiple devices as a group.

[0666] (Note 6) A program as described in any of Appendix 1 to 5, wherein in the calculation step, it determines, as a simulation, whether the device relating to the acquired design data meets the requirements in the space environment, and in the presentation step, it presents the result of the determination of whether the device meets the requirements in the space environment.

[0667] (Note 7) The program described in Appendix 6 displays a 3D model of the device corresponding to the acquired design data in the steps presented, and displays the result of the determination by associating it with the objects that make up the displayed 3D model.

[0668] (Note 8) The program described in Appendix 6, wherein, in the calculation step, if it is determined that the device relating to the acquired design data does not meet the requirements in the space environment, the program identifies and presents each parameter item corresponding to the unmet requirements, and if the device does not meet the requirements in the space environment, the program presents each parameter item corresponding to the identified unmet requirements.

[0669] (Note 9) The program described in Appendix 8 determines whether the acquired design data meets the requirements of the space environment by prompting a large-scale language model to respond whether or not the acquired design data meets the requirements of the space environment.

[0670] (Note 10) A program as described in any of Appendix 8 to 9, which determines whether the device related to the acquired design data can perform the expected control, based on the communication constraints in the space environment, in order to determine that it does not meet the requirements in the space environment.

[0671] (Note 11) A program as described in any of Appendix 1 to 10, wherein in the calculation step, it identifies one or more specifications permissible in a space environment based on acquired design data, and in the presentation step, it presents the identified one or more specifications.

[0672] (Note 12) A method for operating a computer comprising a computer processor and memory, wherein the computer is configured to store parameters of each item affecting the control of equipment in a space environment in the memory, the method comprising the steps of: the computer processor acquiring design data relating to the design of a device; the computer processor calculating a simulation of the device based on the parameters stored in the memory when the device based on the accepted design data is operated in a space environment; and presenting the results of the simulation.

[0673] (Note 13) An information processing device configured to store parameters of each item that affect the control of equipment in the space environment in a storage unit, wherein the control unit of the information processing device performs the steps of: acquiring design data related to the design of a device; calculating a simulation of the device based on the parameters stored in the storage unit when the device based on the received design data is operated in the space environment; and presenting the results of the simulation.

[0674] (Note (Second Embodiment))

[0675] (Note 1) A program for operating a computer comprising a computer processor and memory, wherein the memory unit stores at least one of the following: information on the operator of a space project, information on the developer of a spacecraft, information on space personnel, and information on a spacecraft; and the program performs the steps of evaluating the likelihood of success of a space project based on at least one of the pieces of information stored in the memory unit, and outputting the evaluated results.

[0676] (Note 2) The computer provides the development company with a process to simulate the operation of the spacecraft design data in the space environment and respond with the simulation results. The memory unit stores information about the spacecraft development company, including information on their past experience in spacecraft development through simulations. In the evaluation step, the program described in Appendix 1 evaluates the probability of success based on the development company's past experience in simulations.

[0677] (Note 3) A program as described in either Appendix 1 or 2, wherein the memory unit stores information on the development company's track record of spacecraft demonstration tests or information on its track record of participating in space projects, and in the evaluation step, the program evaluates the likelihood of success based on at least one of the information on the track record of spacecraft demonstration tests or information on its track record of participating in space projects.

[0678] (Note 4) A program described in any of the appendices 1 to 3, wherein the memory unit stores information on space personnel, specifically information on the development company's personnel's development track record, or information on the development company's personnel's participation in space projects, and in the evaluation step, the program evaluates the likelihood of success based on at least one of the development company's personnel's development track record or the development company's personnel's participation in space projects.

[0679] (Note 5) The memory unit stores information on astronauts' flight performance as space personnel information, and in the evaluation step, the program assesses the likelihood of success based on the astronauts' flight performance information, as described in one of the appendices 1 to 4.

[0680] (Note 6) The memory unit stores information about the spacecraft's performance, and in the evaluation step, the program evaluates the probability of success based on the information about the spacecraft's performance, as described in any of the appendices 1 to 5.

[0681] (Note 7) The memory unit stores information about the spacecraft, including information about the spacecraft's manufacturing equipment, processing equipment, and other equipment used to create the spacecraft. In the evaluation step, the program evaluates the likelihood of success based on the information about the equipment used to create the spacecraft, as described in any of the appendices 1 to 6.

[0682] (Note 8) A program described in any of the appendices 1 to 7, which, in the evaluation step, compares information from stakeholders of multiple space projects to relatively assess the likelihood of success of a space project, and in the output step, outputs the results of the relative assessment.

[0683] (Note 9) A program described in any of the appendices 1 to 8, which assesses the likelihood of success in the evaluation step based on whether or not the spacecraft of a space project meets predetermined criteria.

[0684] (Note 10) A program as described in any of Appendix 1 to 9, wherein the memory unit stores information on each space project and whether or not each space project achieved its intended objectives, and in the evaluation step, it evaluates the likelihood of success of the first space project based on information on at least one of the persons or spacecraft of the first space project, and information on at least one of the persons or spacecraft of a second space project that was carried out in the past, and whether or not the second space project achieved its intended objectives.

[0685] (Note 11) In the output step, the program outputs a screen displaying the evaluation results to the user making the investment or loan, and the program further includes a step of receiving an operation from the user making the investment or loan to invest in or lend to the space project on the screen displaying the evaluation results, and in response to the operation to make the investment or loan, the program stores the user's information regarding the space project in the memory, as described in any of the appendices 1 to 10.

[0686] (Note 12) The program described in Appendix 11 further causes the processor to perform a step of determining the benefits to be granted to users who invest or finance the space project based on the revenue generated when the space project generates revenue through commercial activities.

[0687] (Note 13) The memory unit stores information about the right to receive benefits based on the revenue generated when a space project generates revenue through commercial activities, and the program, as described in Appendix 12, causes the processor to execute the step of granting rights to users who invest or provide loans, and allowing users to trade those rights among themselves.

[0688] (Note 14) In the output step, the program outputs a screen to stakeholders of the space project showing the evaluation results of the space project, and the program further includes the steps of determining the insurance premium and other insurance conditions for the space project based on the evaluation results of the space project, accepting an operation from stakeholders of the space project to apply for insurance for the space project while displaying the insurance premium and other insurance conditions on the screen showing the evaluation results, and storing in the memory that an application for insurance for the space project has been made in response to the application for insurance, as described in any of the appendices 1 to 13.

[0689] (Note 15) A method performed by a computer comprising a computer processor and a memory unit, wherein the memory unit stores information of the operator of a space project, information of the developer of a spacecraft, information of space personnel, and information of a spacecraft, and the method performs the steps of evaluating the feasibility of the space project based on at least one of the pieces of information stored in the memory unit, and outputting the evaluated results.

[0690] (Note 16) An information processing device comprising a control unit and a memory unit, wherein the memory unit stores information of the operator of a space project, information of the developer of a spacecraft, information of space personnel, and information of a spacecraft, and the control unit performs the steps of evaluating the feasibility of the space project based on at least one of the pieces of information stored in the memory unit, and outputting the evaluated results.

[0691] (Note (Third Embodiment))

[0692] (Note 1) A program for operating a computer having one or more computer processors, wherein the memory unit stores at least one of the following: information on the personnel's track record of participating in space projects, or information on the personnel's track record of developing spacecraft, and the program causes one or more computer processors to perform the steps of evaluating the personnel based on at least one of the information stored in the memory unit, and outputting information based on the evaluated results.

[0693] (Note 2) The program described in Appendix 1 evaluates the compensation that should be paid to personnel for work related to space projects in the evaluation step, and outputs the results of the evaluation of the compensation that should be paid to personnel for work related to space projects as information based on the evaluation results in the output step.

[0694] (Note 3) The program described in Appendix 2 stores information on the annual salary of personnel in space development organizations based on their performance in the memory unit, and in the evaluation step, it refers to this information on the annual salary of personnel in space development organizations based on their performance to evaluate the compensation that should be given to the personnel being evaluated.

[0695] (Note 4) A program described in any of Appendix 2 or 3, which, in the evaluation step, evaluates the compensation of an employee based on at least one of the following: information from the employee's previous organization or information from the prospective employer, including potential employers.

[0696] (Note 5) The program described in Appendix 4 evaluates the compensation of personnel in the evaluation step, depending on whether or not they are transferring from an organization with a certain level of track record in organizational development or operations.

[0697] (Note 6) The program is one of the programs described in any of Appendix 4 to 5, which further causes one or more computer processors to perform a step of receiving an operation from the user to specify a new organization, and in the output step, outputs the result of evaluating the employee's compensation based on at least one of the information of the employee's current organization or the information of the new organization, including potential new organizations, in response to the operation to specify a new organization.

[0698] (Note 7) A program as described in any of Appendix 2 to 6, which stores information on the compensation currently given to an employee or information on the employee's desired compensation in a memory unit, and in the output step outputs information indicating the degree of discrepancy between the evaluation result of the compensation that should be given to the employee compared to the compensation currently given to the employee being evaluated or the employee's desired compensation.

[0699] (Note 8) The program is one of the programs described in any of Appendix 2 to 7, which causes one or more computer processors to perform the following actions: to present to a job-seeking user the results of an evaluation of the user; to accept an action from the job-seeking user indicating their desire to change jobs on the screen where the evaluation results of the user are presented; and to present to the job-seeking user, in response to the action indicating their desire to change jobs, job offers from recruiting organizations.

[0700] (Note 9) A program described in any of Appendix 1 to 8, in which, in the evaluation step, the performance record of each individual in developing spacecraft is used as the population, and the individual being evaluated is evaluated according to the position of their performance record.

[0701] (Note 10) A program described in any of the appendices 1 to 9, in which the personnel are evaluated based on at least one of the following in the evaluation step: information on the scale of the space projects in which the personnel participated, or information on the entity responsible for the space projects in which the personnel participated.

[0702] (Note 11) In the evaluation step, a space project in which personnel have participated is a program as described in Appendix 10, which includes at least one of the following: having a track record of developing a spacecraft related to the space project, or having a track record of operating the space project.

[0703] (Note 12) A program described in any of the appendices 1 to 11, which stores information in its memory unit indicating whether or not a person is suitable as an individual, and in the evaluation step, evaluates the person based on the information regarding whether or not they are suitable.

[0704] (Note 13) A program described in any of the appendices 1 to 12, which stores information on evaluations of personnel from other individuals in its memory unit, and in the evaluation step, if the evaluation of the personnel being evaluated from other individuals is above a certain level, the personnel are deemed suitable, and the personnel are evaluated based on the evaluations from other individuals.

[0705] (Note 14) The program described in Appendix 13 stores information about the personal network of an individual as information about the influence that individual has on other individuals in its memory unit, and in the evaluation step, evaluates the individual based on the personal network information of the individual.

[0706] (Note 15) A method performed by a computer having one or more computer processors, The memory unit stores at least one of the following: information on the personnel's track record of participating in space projects, or information on the personnel's track record of developing spacecraft. The method involves one or more computer processors, A step of evaluating personnel based on at least one of the pieces of information stored in the memory unit, A method for performing the steps of outputting information based on the evaluated results.

[0707] (Note 16) An information processing device comprising a control unit, wherein a memory unit stores at least one of the following: information on the personnel's track record of participating in space projects, or information on the personnel's track record of developing spacecraft, and the control unit performs the steps of evaluating the personnel based on at least one of the information stored in the memory unit, and outputting information based on the evaluated results.

[0708] (Note (Fourth Embodiment))

[0709] (Note 1) A program for operating a computer having one or more computer processors, wherein the memory unit records information of entities conducting space development and information of the entities' past performance in space development in association with each other, and the program causes one or more computer processors to execute the following steps: acquiring information of a request for work related to a space project; extracting entities with experience corresponding to the request based on the acquired information of the request and the information of each entity's past performance in space development stored in the memory unit; and presenting the extracted entities and the information of the extracted entities' past performance in space development to the user making the request.

[0710] (Note 2) The program described in Appendix 1 includes, in the memory unit, information on the space development achievements of personnel belonging to the entity as information on the entity's achievements in space development, in the extraction step, extracting personnel who have experience handling tasks related to the requested content by referring to the memory unit, and in the presentation step, presenting the extracted entity to the user, including presenting the personnel or the entity to which the personnel belong.

[0711] (Note 3) The memory unit is configured to store information related to space projects, and the memory unit includes information on the space projects in which the personnel have participated as information on the personnel's achievements in space development. In the extraction step, the program refers to the memory unit to identify information on space projects related to the requested work and extracts the personnel who participated in the identified space projects, as described in Appendix 2.

[0712] (Note 4) The memory unit is configured to store information related to spacecraft, and the memory unit includes information on the achievements of personnel in space development, specifically information on the achievements of spacecraft developed by those personnel. In the extraction step, the memory unit is referenced to identify information on spacecraft related to the requested work, and the personnel who developed the identified spacecraft are extracted, as described in one of the appendices 2 to 3.

[0713] (Note 5) The computer provides the subject with a process to simulate the operation of spacecraft design data in a space environment and respond with the simulation results. The memory unit stores information on the personnel's experience in space development, specifically information on their experience in spacecraft development through simulations. In the extraction step, the program extracts personnel who have worked on spacecraft development related to the requested tasks by referring to the experience in spacecraft development through simulations, as described in Appendix 4.

[0714] (Note 6) A program described in any of the appendices 4 to 5, wherein the memory unit includes, as information on the performance of spacecraft developed by personnel, at least one of the following: the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project, and in the extraction step, identifies information on spacecraft related to the work related to the request, and includes identifying the spacecraft based on at least one of the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project.

[0715] (Note 7) The memory unit stores information about personnel, including a score that evaluates each person based on their achievements in space development. In the extraction step, the program extracts personnel based on their scores, as described in any of the appendices 2 to 6.

[0716] (Note 8) A program as described in any of Appendix 1 to 7, wherein the memory unit is configured to store at least one of either information relating to a space project or information relating to a spacecraft, and the memory unit includes, as information on the entity's achievements in space development, at least one of the entity's achievements in spacecraft development or the entity's achievements in space projects in which the entity participated, and in the extraction step, the program identifies information on a spacecraft or space project related to the work related to the request by referring to the memory unit, and extracts the entity that developed the identified spacecraft or participated in the space project.

[0717] (Note 9) The computer provides the subject with a process to simulate the operation of spacecraft design data in a space environment and respond with the simulation results. The memory unit stores information on the subject's achievements in space development, specifically information on the subject's achievements in spacecraft development through simulations. In the extraction step, the program extracts the subject that has developed a spacecraft related to the requested work by referring to the subject's achievements in spacecraft development through simulations, as described in Appendix 8.

[0718] (Note 10) A program as described in any of Appendix 8 to 9, wherein the memory unit includes, as information on the performance of a spacecraft developed by the entity, at least one of the following: the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project, and in the extraction step, identifies information on a spacecraft related to the work related to the request, and includes identifying the spacecraft based on at least one of the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project.

[0719] (Note 11) A program described in any of Appendix 8 to 10, wherein the memory unit stores information on space projects, and this information includes information on entities that participated in the space projects and information on the funds obtained by the space projects. In the extraction step, the program refers to the memory unit to identify information on space projects related to the requested work based on the information on the funds obtained by the space projects, and extracts information on entities that participated in the identified space projects.

[0720] (Note 12) In the steps to acquire the technology, the program described in any of the appendices 1 to 11 includes, as part of the requested work, at least one of the following: design, manufacture, or fabrication of spacecraft related to a space project, or development of software to control the spacecraft.

[0721] (Note 13) The program described in Appendix 12 includes, in the acquisition step, data related to the requested work for the space project (e.g., specifications, design documents, etc.) to be presented to the recipient of the request, such as designers, manufacturers, processors, and software developers, in the information of the request, and in the extraction step, extracts entities that have experience in handling the requested work based on the request data.

[0722] (Note 14) A program described in any of the appendices 1 to 13, which, in the step of presenting the information, presents to the user, along with the extracted entities, information on the extracted entities' achievements in space development, specifically information on achievements relevant to the requested tasks.

[0723] (Note 15) The program is one of the programs described in any of Appendix 1 to 14, which causes one or more computer processors to execute the steps of: receiving an operation from a user to specify a presented entity; requesting the specified entity to perform the requested tasks; and storing in a memory unit that a request for tasks has been received from a user, in association with the information of the specified entity.

[0724] (Note 16) The program described in Appendix 15, which, in the acceptance step, receives information on the transaction price related to the request for services from the user, stores the transaction price information in the memory unit in association with the fact that the request has been accepted, and in the presentation step, by referring to the transaction price information in the memory unit, presents the user with the extracted entity information along with the transaction price information that can be used as a reference when requesting services.

[0725] (Note 17) A method for operating a computer having one or more computer processors, wherein a memory unit records information of entities that conduct space development and information of the entities' past performance in space development in association with each other, the method comprising: one or more computer processors performing the steps of: acquiring information of a request for work related to a space project; extracting entities that have experience corresponding to the request based on the acquired information of the request and the information of each entity's past performance in space development stored in the memory unit; and presenting the extracted entities and the information of the extracted entities' past performance in space development to the user making the request.

[0726] (Note 18) An information processing device, wherein a memory unit records information of entities conducting space development and information of the entities' achievements in space development in association with each other, and the control unit of the information processing device performs the following steps: acquiring information of a request for work related to a space project; extracting entities with achievements corresponding to the request based on the acquired information of the request and the information of each entity's achievements in space development stored in the memory unit; and presenting the extracted entities and the information of the extracted entities' achievements in space development to the user making the request. [Explanation of Symbols]

[0727] 1: System 10: Terminal 10A: Terminal 13: Input device 14: Output device 15: Memory 16: Storage 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 30: Terminal 40: Terminal 80: Network 95: Server 96: Server 97: Server 111: Antenna 112: Antenna 120: First Communications Department 121: Second Communications Department 130: Input device 131: Device 132: Display 140: Audio Processing Unit 141: Mike 142: Speaker 150: Location Information Sensor 160: Camera 170: Motion Sensor 180: Storage section 181: User Information 182: Ground aircraft design information 190: Control Unit 191: Operation Reception Section 192: Transceiver Unit 193: Data Processing Unit 194: Notification Control Unit 195: Memory Control Unit 201: Communications Department 202: Storage section 203: Control Unit 211: User Database 212: Constraint Database 213: Spacecraft Sample Database 214: Astronaut Database 215: Space Project Database 216: Design History Database 217: Matching Database 218: Space Development Human Resources Database 219: Development Spacecraft Database 220: Insurance Application History Database 221: Financial Support History Database 222: Rights Transaction History Database 223: Talent Matching Database 224: Desired Talent Database 1000: Operation screen 1002: User information display area 1004: Space Project Display Area 1006: Switching operation reception unit 1008: Member candidate display area 1010: Candidate details display area 1012: Participation Request Reception Department 1014: Participating Members Display Area 1016: Participant details display area 1018: Participation Operation Reception Department 1020: Simulation display area 1022: Device list display area 1024: First device display area 1026: Second device display area 1028: Third device display area 1030: Exploration Location Designation Reception Department 1032 :Result display area 1034: First object 1036: Second object 1038: The third object 1040: Registration Operation Reception Department 1042: Registered data list display area 1044: Design data display area 1046: Simulation result display area 1048: Sample data display area 1050: First sample data display area 1052: Second sample data display area 1054: Three-dimensional model display area 1056: Warning display area 1058: Score display area 1060 :Detail display area 1062: Application Processing Department 1064: Confirmation Operation Reception Department 1066: Confirmation Operation Reception Department 1068: Other project display area 1070: Score display area 1072: Confirmation Operation Reception Department 1074: Loan and Investment Operations Reception Department 1076: Confirmation Operation Reception Department 1078: Copyright Notice Area 1080: Confirmation Operation Reception Department 1082: Transaction display area 1084: Order display area 1086: Order Processing Department 1088: Confirmation Operation Reception Department 2041: Receiver control module 2042: Transmit control module 2043: User Management Module 2044: Project Registration Module 2045: Simulation Processing Module 2046: Matching Processing Module 2047: Score calculation module 2048: Transaction acceptance module 2049: Talent Assessment Module 2050: Talent Matching Module 2600: Operation screen 2700: Operation screen 2800: Operation screen 3500: Operation screen 3502: User information display area 3504: Reward score display area 3506: Score details display area 3508: Designation section for disclosure / non-disclosure 3510: Career Selection Screen 3512: Career Designation Department 3514: Verification Operation Unit 3516 :Generation operation section 3518: Matching Selection Screen 3520: Verification Operation Unit 3522: Matching Designation Section 3524: Operation screen 3526: User information display area 3528: Desired Personnel Registration Screen 3530: Requirements Specification Section 3532: Predicted score display area 3534: Registration Operation Unit 3536: Candidate display screen 3538: Recruitment Requirements Viewing Operation Unit 3540: Predicted score display area 3542: Personnel Verification and Operation Department 3544: Past recruitment viewing screen 3546: Past Recruitment Viewing Operation Unit 3548: Predicted score display area 3550: Past Application Confirmation Operation Unit 3552: Offer display screen 3554: Recruitment Requirements Viewing Operation Unit 3556: Application Operation Department 3558: Recruitment Viewing Screen 3560:Recruitment content display area 3562: Predicted score display area 3564: Search Operation Unit 3566: Application Operations Department

Claims

1. A program for operating a computer having one or more computer processors, In the memory unit, information about the entity conducting space development and information about the entity's achievements in space development are recorded in association with each other. The program is configured on one or more computer processors. Steps to obtain information about the details of the request for work related to the space project, Based on the acquired information on the request and the information on the space development track record of each entity stored in the memory unit, the step of extracting entities that have a track record corresponding to the request, A program that performs the steps of presenting the extracted entities and information on the extracted entities' achievements in space development to the user who made the aforementioned request.

2. The aforementioned memory unit includes information on the achievements of the entity in space development, specifically information on the achievements of personnel belonging to that entity in space development. In the extraction step, by referring to the memory unit, personnel who have experience handling tasks related to the requested content are extracted. The program according to claim 1, wherein the step of presenting the extracted entity includes presenting the entity to the user, namely the individual or the entity to which the individual belongs.

3. The aforementioned memory unit is configured to store information related to the space project, The memory unit includes, as information on the personnel's achievements in space development, information on space projects in which the personnel participated. The program according to claim 2, wherein in the extraction step, by referring to the memory unit, information on space projects related to the work related to the request is identified, and personnel who participated in the identified space projects are extracted.

4. The memory unit is configured to store information relating to the spacecraft, The memory unit includes, as information on the personnel's achievements in space development, information on the achievements of spacecraft developed by the personnel. The program according to claim 2, wherein in the extraction step, by referring to the memory unit, information on spacecraft related to the work related to the request is identified, and personnel who developed the identified spacecraft are extracted.

5. The computer provides the subject with a process to perform a simulation of what would happen if the spacecraft design data were operated in a space environment, and to respond with the simulation results. The memory unit stores information on the personnel's achievements in space development, specifically information on their achievements in developing the spacecraft through simulations. The program according to claim 4, wherein in the extraction step, the program extracts personnel who have worked on the development of spacecraft related to the requested work by referring to the results of the spacecraft development obtained through the simulation.

6. The memory unit includes, as information on the performance of the spacecraft developed by the personnel, at least one of the following: the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project. The program according to claim 4, wherein the extraction step includes identifying information about a spacecraft related to the work related to the request, and the identification of the spacecraft is based on at least one of the following: the spacecraft has undergone demonstration testing or the spacecraft has been operated in a space project.

7. The memory unit stores information about the personnel, including a score that evaluates the personnel based on their achievements in space development. The program according to claim 2, wherein in the extraction step, the program extracts the personnel based on the personnel's score.

8. The memory unit is configured to store at least one of the following: information relating to a space project or information relating to a spacecraft. The memory unit includes, as information on the entity's achievements in space development, at least one of the entity's achievements in developing spacecraft or the entity's achievements in space projects in which it participated. The program according to claim 1, wherein in the extraction step, by referring to the memory unit, it identifies information about a spacecraft or space project related to the work related to the request, and extracts the entity that developed the identified spacecraft or participated in the space project.

9. The computer provides the subject with a process to perform a simulation of what would happen if the spacecraft design data were operated in a space environment, and to respond with the simulation results. The memory unit stores information on the subject's achievements in space development, specifically information on the development achievements of the spacecraft based on the simulations. The program according to claim 8, wherein in the extraction step, the program extracts entities that have developed spacecraft related to the requested work by referring to the results of the spacecraft development obtained through the simulation.

10. The memory unit includes, as information on the performance of the spacecraft developed by the entity, at least one of the following: the performance of the spacecraft after undergoing demonstration tests, or the performance of the spacecraft in operation in a space project. The program according to claim 8, wherein the extraction step includes identifying information about a spacecraft related to the work related to the request, and the identification of the spacecraft is based on at least one of the following: the spacecraft has undergone demonstration testing or the spacecraft has been operated in a space project.

11. The memory unit stores information about the space project, and this information includes information about the entities that participated in the space project and information about the funds obtained by the space project. The program according to claim 8, wherein in the extraction step, by referring to the memory unit, it identifies information on space projects related to the requested work based on information on the funds obtained by the space project, and extracts information on entities that participated in the identified space project.

12. The program according to claim 1, wherein the steps for obtaining the information include, as work related to the requested content, at least one of the following: design, manufacture, and processing of a spacecraft related to a space project, and development of software to control the spacecraft.

13. In the aforementioned acquisition step, the information regarding the request includes data related to the details of the space project's work (e.g., specifications, design documents, etc.) that will be presented to the recipient of the request, such as designers, manufacturers, processors, and software developers. The program according to claim 12, wherein in the extraction step, it extracts entities that have a track record corresponding to the content of the request based on the request data.

14. The program according to claim 1, wherein in the step described above, the program presents to the user, along with the extracted entities, information on the extracted entities' achievements in space development, specifically information on achievements corresponding to the requested work.

15. The program further provides the following to one or more computer processors: The steps include receiving an operation from the user to specify the presented entity and an operation to request the specified entity to perform the tasks related to the request, The steps include: storing in the storage unit that a business request has been received from the user, in association with the information of the designated entity; The program according to claim 1, which causes to execute.

16. In the aforementioned acceptance step, information regarding the transaction price related to the request for the aforementioned services is received from the user. The aforementioned memory unit stores transaction price information in association with the fact that the request has been received. The program according to claim 15, wherein in the step described above, by referring to the transaction price information in the storage unit, the program presents to the user, along with the extracted entity information, information on the transaction price that can be used as a reference when requesting the above-mentioned work.

17. A method for operating a computer having one or more computer processors, In the memory unit, information about the entity conducting space development and information about the entity's achievements in space development are recorded in association with each other. The above method involves one or more computer processors, Steps to obtain information about the details of the request for work related to the space project, Based on the acquired information on the request and the information on the space development track record of each entity stored in the memory unit, the step of extracting entities that have a track record corresponding to the request, A method for performing the following steps: presenting the extracted entities and information on the extracted entities' achievements in space development to the user who made the request.

18. An information processing device, In the memory unit, information about the entity conducting space development and information about the entity's achievements in space development are recorded in association with each other. The control unit of the information processing device, Steps to obtain information about the details of the request for work related to the space project, Based on the acquired information on the request and the information on the space development track record of each entity stored in the memory unit, the step of extracting entities that have a track record corresponding to the request, An information processing device that performs the steps of presenting to the user who made the request the extracted entities and information on the extracted entities' achievements in space development.

Images