Service provision support device, service provision support method, program, and recording medium

Abstract

To provide a service provision support device, a service provision support method, and a program that quickly respond to a change in customer needs and facilitate management of provision of a service.SOLUTION: A service provision support device includes a customer information acquisition unit, a provider information acquisition unit, a service ticket information generation unit, and a service information output unit. The customer information acquisition unit acquires customer service information, the provision of which is requested by a customer. The provider information acquisition unit acquires provision service information proposed by a service provider. The service ticket information generation unit generates a service ticket information for every customer based on the customer service information and provision service information. The service information output unit outputs the service ticket information. The customer information acquisition unit acquires information on a purchased ticket purchased by the customer in the service ticket information. The service information output unit outputs the purchased ticket information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a service provision support device, a service provision support method, a program, and a recording medium.

Background Art

[0002] System integration (SI) is a service that undertakes tasks from the planning, development, operation, and maintenance of information systems. As the target information system becomes more complex and extensive, the number of tasks tends to increase, become more complex, and take longer. On the other hand, due to the progress of cloud computing and the like, requirements are constantly changing, so there is a need for so-called agile (sensitive, rapid) development. For example, Patent Document 1 discloses a system development support program and a system development support method that automatically support design not only for waterfall-type but also for agile-type system development.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, even in agile-type system development, there has been no technology that can quickly respond to changes in customer needs and is easy to manage system development. This problem is common not only to information system development but also to the field of providing services (tasks) according to customer needs.

[0005] Therefore, an object of the present invention is to provide a service provision support device, a service provision support method, and a program that can quickly respond to changes in customer needs and are easy to manage service provision.

Means for Solving the Problems

[0006] To achieve the above objective, the service provision support device of the present invention is It includes a customer information acquisition unit, a provider information acquisition unit, a service ticket information generation unit, and a service information output unit. The aforementioned customer information acquisition unit acquires customer service information requested by the customer, The aforementioned provider information acquisition unit acquires the service information proposed by the service provider, The service ticket information generation unit generates service ticket information for each customer based on the customer service information and the provided service information. The service information output unit outputs the service ticket information, The customer information acquisition unit acquires the purchase ticket information of the customer from the service ticket information, The service information output unit outputs the purchased ticket information.

[0007] The service provision support method of the present invention is This includes a customer information acquisition process, a provider information acquisition process, a service ticket information generation process, and a service information output process. The aforementioned customer information acquisition process acquires customer service information that the customer requests to be provided. The aforementioned provider information acquisition process acquires the service information proposed by the service provider, The service ticket information generation process generates service ticket information for each customer based on the customer service information and the provided service information. The service information output step outputs the service ticket information, The customer information acquisition step acquires the purchase ticket information of the customer from the service ticket information, The service information output step outputs the purchased ticket information.

[0008] The program of the present invention includes a procedure for acquiring customer information, a procedure for acquiring provider information, a procedure for generating service ticket information, and a procedure for outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, This is a program that causes a computer to execute each of the aforementioned steps.

[0009] The recording medium of the present invention includes a procedure for acquiring customer information, a procedure for acquiring provider information, a procedure for generating service ticket information, and a procedure for outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, This is a computer-readable recording medium that stores a program for causing a computer to perform each of the aforementioned procedures. [Effects of the Invention]

[0010] According to the present invention, it is possible to respond quickly to changes in customer needs and to manage service provision easily. For example, when the present invention is applied to information system development (e.g., system integration), it is possible to respond quickly to changes in customer needs and to manage the system easily. [Brief explanation of the drawing]

[0011] [Figure 1] FIG. 1 is a block diagram showing a configuration example of a service provision support apparatus according to Embodiment 1. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of the service provision support apparatus according to Embodiment 1. [Figure 3] FIG. 3 is a flowchart showing an example of the processing of the service provision support method according to Embodiment 1. [Figure 4] FIG. 4 is a block diagram showing a configuration example of a service provision support apparatus according to Embodiment ②. [Figure 5] FIG. 5 is a block diagram showing an example of the hardware configuration of the service provision support apparatus according to Embodiment ②. [Figure 6] FIG. 6 is a diagram showing an example of a service provision support apparatus according to Embodiment 3. [Figure 7] FIG. 7 is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 8] FIG. 8 is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 9] FIG. 9 is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 10] FIG. 10 is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 11A] FIG. 11A is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 11B] FIG. 11B is a diagram showing an example of a service provision support method according to Embodiment 3. [Figure 12] FIG. 12 is a diagram showing an example of a service provision support method according to Embodiment 3.

[0012] The service provision support apparatus of the present invention, for example, further includes a service provision contract section, The service provision contract section generates contract conclusion information in which a service provision contract is concluded between the customer and the provider regarding the provision of the service related to the purchased service ticket based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output unit outputs contract information that includes at least one of the contract conclusion information and the contract termination information. This approach is also acceptable.

[0013] In the service provision support device of the present invention, for example, The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation unit generates the ticket information associated with the service menu information based on the service list information. This approach is also acceptable.

[0014] The service provision support device of the present invention is, for example, Furthermore, it includes a customer menu generation unit, The customer service information includes information on the customer's selection of the options, The customer menu generation unit generates a customer menu for each customer from the service list information based on the selection information. This approach is also acceptable.

[0015] In the service provision support device of the present invention, for example, The customer service information includes priority information for the services requested by the customer. The customer menu generation unit generates the customer menu, which includes priority information for the service menu, based on the priority information. This approach is also acceptable.

[0016] In the service provision support device of the present invention, for example, The provider information acquisition unit acquires consumption ticket information relating to services for which service provision has been completed from the purchased ticket information. Furthermore, including the Services Management Department, The Service Management Department manages the progress of services provided by the provider based on the consumption ticket information. This approach is also acceptable.

[0017] In the service provision support device of the present invention, for example, The Service Management Department, based on the Consumption Ticket Information, identifies services that have not yet been provided within the Purchase Ticket Information, and generates information on services that are currently being worked on from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output unit outputs the service information for ongoing work and the service information for services not yet started. This approach is also acceptable.

[0018] In the service provision support device of the present invention, for example, The Service Management Department calculates the remaining ticket balance based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket balance is insufficient to perform the services requested by the customer, it generates additional ticket information. The service information output unit outputs the ticket additional information. This approach is also acceptable.

[0019] In the service provision support device of the present invention, for example, The customer information acquisition unit acquires additional purchase ticket information from the service ticket information that the customer has purchased. The service information output unit outputs the additional purchase ticket information. This approach is also acceptable.

[0020] In the service provision support device of the present invention, for example, The customer information acquisition unit generates transfer ticket information by reallocating the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output unit outputs the transfer ticket information. This approach is also acceptable.

[0021] The service provision support device of the present invention is, for example, Furthermore, including the Service Provision Contracts Department, The Service Provision Contract Department generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output unit outputs contract information including at least one of the contract conclusion information and the contract termination information. The Service Management Department manages, based on the contract information, the orders placed by the customer for services, the acceptance of service orders by the provider, and the progress of services by the provider. This approach is also acceptable.

[0022] In the service provision support device of the present invention, for example, the service may be a service related to information system development.

[0023] In the service provision support device of the present invention, for example, The provider information acquisition unit acquires the design document information for the information system development, The aforementioned Service Management Department registers and manages the aforementioned design document information, The service information output unit outputs the design document information. This approach is also acceptable.

[0024] The service provision support method of the present invention is, for example, Furthermore, including the service provision contract process, The service provision contract process generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output step outputs contract information including at least one of the contract conclusion information and the contract termination information. This approach is also acceptable.

[0025] In the service provision support method of the present invention, for example, The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation process generates the ticket information associated with the service menu information based on the service list information. This approach is also acceptable.

[0026] The service provision support method of the present invention is, for example, Furthermore, including the customer menu generation process, The customer service information includes information on the customer's selection of the options, The customer menu generation process generates a customer menu for each customer from the service list information based on the selection information. This approach is also acceptable.

[0027] In the service provision support method of the present invention, for example, The customer service information includes priority information for the services requested by the customer. The customer menu generation process generates the customer menu, which includes priority information for the services to be provided, based on the priority information. This approach is also acceptable.

[0028] In the service provision support method of the present invention, for example, The provider information acquisition step acquires consumption ticket information related to services for which service provision has been completed from the purchased ticket information, Furthermore, including the service management process, The service management process manages the progress of services provided by the provider based on the consumption ticket information. This approach is also acceptable.

[0029] In the service provision support method of the present invention, for example, The service management process, based on the consumption ticket information, identifies services that have not yet been provided within the purchase ticket information, and generates service information for ongoing work from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output step outputs the service information for ongoing work and the service information for services not yet started. This approach is also acceptable.

[0030] In the service provision support method of the present invention, for example, The service management process calculates the remaining ticket quantity based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket quantity is insufficient to perform the service requested by the customer, it generates additional ticket information. The service information output step outputs the ticket additional information. This approach is also acceptable.

[0031] In the service provision support method of the present invention, for example, The customer information acquisition step acquires additional purchase ticket information of the customer that has made an additional purchase from the service ticket information, The service information output step outputs the additional purchase ticket information. This approach is also acceptable.

[0032] In the service provision support method of the present invention, for example, The customer information acquisition step generates transfer ticket information by reallocating the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output step outputs the transfer ticket information. This approach is also acceptable.

[0033] The service provision support method of the present invention is, for example, Furthermore, including the service provision contract process, The service provision contract process generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output step outputs contract information including at least one of the contract conclusion information and the contract termination information. The service management process manages, based on the contract information, the customer's order for services, the provider's acceptance of the service, and the provider's progress of the services. This approach is also acceptable.

[0034] In the service provision support method of the present invention, for example, the service may be a service related to information system development.

[0035] In the service provision support method of the present invention, for example, The provider information acquisition step acquires the design document information for the information system development, The aforementioned service management process registers and manages the design document information, The service information output step outputs the design document information. This approach is also acceptable.

[0036] The program of the present invention is, for example, a program that causes a computer to execute each step of the service provision support method of the present invention. The recording medium of the present invention is, for example, a computer-readable recording medium on which the program of the present invention is recorded.

[0037] In the present invention, the services to be provided are not particularly limited and include, for example, information system development (SI, etc.), consulting, search services (prior literature search, etc.), and various surveys (environmental surveys, population surveys, health surveys, business condition surveys, etc.).

[0038] Embodiments of the present invention will be described below with reference to the figures. The present invention is not limited to the following embodiments. In the following figures, the same parts are denoted by the same reference numerals. Furthermore, unless otherwise specified, the descriptions of each embodiment can be used interchangeably with those of the others, and unless otherwise specified, the configurations of each embodiment can be combined.

[0039] [Embodiment 1] Figure 1 is a block diagram showing an example configuration of the service provision support device 10A of this embodiment. As shown in Figure 1, the device 10A includes a customer information acquisition unit 11, a provider information acquisition unit 12, a service ticket information generation unit 13, and a service information output unit 14. The device 10A may also include an input unit, an output unit, a display unit, and / or a storage unit, although these are not shown.

[0040] The device 10A may be, for example, a single device including the aforementioned parts, or it may be a device in which the aforementioned parts can be connected via a communication network. Furthermore, the device 10A can be connected to an external device described later via the communication network. The communication network is not particularly limited and can use a known network, for example, it may be wired or wireless. Examples of the communication network include the Internet, WWW (World Wide Web), telephone lines, LAN (Local Area Network), SAN (Storage Area Network), DTN (Delay Tolerant Networking), LPWA (Low Power Wide Area), L5G (Local 5G), etc. Examples of wireless communication include Wi-Fi (registered trademark), Bluetooth (registered trademark), Local 5G, LPWA, etc. The wireless communication may be in the form of direct communication between devices (Ad Hoc communication), infrastructure communication, indirect communication via an access point, etc. The device 10A may be, for example, incorporated into a server as a system. Furthermore, the device 10A may be, for example, a personal computer (PC, e.g., desktop or notebook type), smartphone, tablet terminal, etc., on which the program of the present invention is installed. The device 10A may also be in the form of cloud computing or edge computing, for example, in which at least one of the above-mentioned parts is on a server and the other parts are on a terminal.

[0041] Figure 2 illustrates a block diagram of the hardware configuration of the device 10A. The device 10A includes, for example, a central processing unit (CPU, GPU, etc.) 101, memory 102, bus 103, storage device 104, input device 105, output device 106, communication device 107, etc. Each part of the device 10A is interconnected via the bus 103 through its respective interface (I / F).

[0042] The central processing unit 101 operates in coordination with other components via controllers (system controller, I / O controller, etc.) and is responsible for the overall control of the device 10A. In the device 10A, the central processing unit 101 executes, for example, the program of the present invention and other programs, and also reads and writes various types of information. Specifically, for example, the central processing unit 101 functions as a customer information acquisition unit 11, a provider information acquisition unit 12, a service ticket information generation unit 13, and a service information output unit 14. The device 10A may also be equipped with other computing devices such as a CPU, GPU (Graphics Processing Unit), APU (Accelerated Processing Unit), or a combination thereof.

[0043] Bus 103 can also be connected to external devices, for example. Examples of such external devices include external storage devices (external databases, etc.), printers, external input devices, external display devices, and external imaging devices. The device 10A can be connected to an external network (the aforementioned communication network) by a communication device 107 connected to bus 103, for example, and can also be connected to other devices via the external network.

[0044] Memory 102 may be, for example, main memory. When the central processing unit 101 performs processing, memory 102 reads various operational programs, such as the program of the present invention, stored in the storage device 104 (described later), and the central processing unit 101 receives data from memory 102 and executes the program. The main memory may be, for example, RAM (random access memory). Alternatively, memory 102 may be, for example, ROM (read-only memory).

[0045] The storage device 104 is also called an auxiliary storage device, for example, in relation to the main memory (primary memory). As described above, the storage device 104 stores an operating program including the program of the present invention. The storage device 104 may be, for example, a combination of a recording medium and a drive for reading and writing to the recording medium. The recording medium is not particularly limited and may be internal or external, for example, an HD (hard disk), CD-ROM, CD-R, CD-RW, MO, DVD, flash memory, memory card, etc. The storage device 104 may be, for example, a hard disk drive (HDD) in which the recording medium and the drive are integrated, or a solid state drive (SSD). If the device 10A includes the storage unit, for example, the storage device 104 functions as the storage unit. The aforementioned storage unit can store, for example, information about the user of this device (the owner of this device, the administrator of this device, the user of this device, etc.) (name, company name, person in charge name, identification number, attribute information (gender, age, affiliated organization, address, contact information, etc.)), customer data, service provider data, data acquired by this device, and information generated by this device.

[0046] In this device 10A, the memory 102 and storage device 104 can also store various types of information, such as log information, information obtained from an external database (not shown) or external devices, information generated by this device 10A, and information used by this device 10A when executing processing. In this case, the memory 102 and storage device 104 may store, for example, the user information and various data of this device as described above. At least some of the information may be stored on an external server other than the memory 102 and storage device 104, or it may be stored in a distributed manner across multiple terminals using blockchain technology or the like.

[0047] The device 10A further includes, for example, an input device 105 and an output device 106. The input device 105 may include, for example, a pointing device such as a touch panel, trackpad, or mouse; a keyboard; imaging means such as a camera or scanner; a card reader such as an IC card reader or magnetic card reader; an audio input means such as a microphone; and so on. The output device 106 may include, for example, a display device such as an LED display or liquid crystal display; an audio output device such as a speaker; a printer; and so on. In this embodiment 1, the input device 105 and the output device 106 are configured separately, but the input device 105 and the output device 106 may be configured as an integrated unit, such as a touch panel display.

[0048] Next, an example of the service provision support method of this embodiment will be described based on the flowchart S10 in Figure 3. The service provision support method of this embodiment is implemented as follows, for example, using the device 10A in Figure 1 or Figure 2. Note that the service provision support method of this embodiment is not limited to the use of the device 10A in Figure 1 or Figure 2.

[0049] First, the customer information acquisition unit 11 acquires customer service information that the customer requests (S11, customer information acquisition step). Next, the provided service information acquisition unit 12 acquires provided service information proposed by the service provider (S12, provided service information acquisition step). Next, the service ticket information generation unit 13 generates service ticket information for each customer based on the customer service information and the provided service information (S13, service ticket information generation step). Next, the service information output unit 14 outputs the service ticket information (S14, service information output step). Next, the customer information acquisition unit 11 acquires purchase ticket information that the customer has purchased from the service ticket information (S15, customer information acquisition step). Then, the service information output unit 14 outputs the purchase ticket information (S16, service information output step).

[0050] In conventional service management systems, customers simply select from a list of services offered by the provider. However, in this invention, tickets are generated from information on both the customer and the service provider, which has the effect of enabling service provision tailored to customer needs.

[0051] In the present invention, "customer service information" includes, for example, questions, requests for quotations, and consultations regarding the provision of services. In the present invention, the output destination of the "service information output unit" is, for example, within this device (e.g., a display device), a customer terminal, a service provider's terminal, or other external devices, and the output method is, for example, display on a display device (display).

[0052] [Embodiment 2] Next, Embodiment 2 of the present invention will be described with reference to Figures 4 to 5.

[0053] Figure 4 is a block diagram showing an example of the configuration of the device 10B of this embodiment, and Figure 5 is a block diagram showing an example of the hardware configuration of the device 10B. As shown in Figures 4 and 5, the device 10B includes a customer information acquisition unit 11, a provider information acquisition unit 12, a service ticket information generation unit 13, and a service information output unit 14, as well as a service provision contract unit 15, a customer menu generation unit 16, and a service management unit 17. Except for these, it is the same as the device 10A and process S10 of Embodiment 1. The processing of the service provision contract unit 15, the customer menu generation unit 16, and the service management unit 17 will be described below. The processing by the service provision contract unit 15, the customer menu generation unit 16, and the service management unit 17 can be appropriately inserted at any position in the flowchart S10 of Figure 3 described in Embodiment 1.

[0054] First, the service provision contract unit 15 will be described. Based on the purchased ticket information, the service provision contract unit 15 generates contract conclusion information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, and generates contract termination information indicating that the service contract has ended, based on the consumed ticket information for services that have been completed within the purchased ticket information. The service information output unit 14 then outputs contract information that includes at least one of the contract conclusion information and the contract termination information.

[0055] Next, the customer menu generation unit 16 will be described. First, if the service information includes service list information, and the service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information, the service ticket information generation unit 13 generates the ticket information associated with the service menu information based on the service list information. Furthermore, if the customer service information includes selection information of the options by the customer, the customer menu generation unit 16 generates a customer menu for each customer from the service list information based on the selection information.

[0056] Furthermore, if the customer service information includes priority information for the services requested by the customer, the customer menu generation unit 16 generates a customer menu that includes priority information for the services to be provided, based on the priority information.

[0057] Next, I will explain the service management unit 17. First, when the provider information acquisition unit 12 acquires consumption ticket information for services that have been completed from the purchased ticket information, the service management unit 17 manages the progress of the services provided by the provider based on the consumption ticket information.

[0058] Furthermore, the service management unit 17 may identify services that have not been provided incomplete from the purchased ticket information based on the consumed ticket information, generate service information for ongoing work from the identified incomplete services, and identify unpurchased service ticket information from the service ticket information and purchased ticket information, and generate unstarted service information from the identified unpurchased ticket information. The service information output unit 14 outputs the service information for ongoing work and the unstarted service information.

[0059] The service management unit 17 then calculates the remaining ticket balance based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket balance is insufficient to perform the service requested by the customer, it may generate additional ticket information. The service information output unit 14 outputs the additional ticket information. In this embodiment, the customer information acquisition unit 11 may acquire additional purchased ticket information from the service ticket information, and the service information output unit 14 may output the additional purchased ticket information. In this embodiment, the customer information acquisition unit 11 may also generate transfer ticket information by reallocating purchased tickets related to incomplete services from the purchased ticket information to the performance of the service for which the remaining ticket balance is insufficient. The service information output unit 14 outputs the transfer ticket information.

[0060] The service management unit 17 may manage the customer's order for services, the provider's acceptance of the service, and the provider's progress of the services based on the contract information output by the service information output unit 14.

[0061] Service management by the Service Management Department 17 is not particularly restricted and may include methods such as displaying progress and ticket information using graphs and tables, and notifying deadlines with alarms or the like as the service progresses.

[0062] [Embodiment 3] Next, Embodiment 3 of the present invention will be described based on Figures 6 to 12. Embodiment 3 is an example of a service related to information system development.

[0063] Figure 6 shows an example of the device according to this embodiment. As shown in the figure, this device has functions for "SI consultation and QA implementation," "SI menu contract," "ticket issuance and management," "SI progress confirmation management," and "design document management," and also has a function to display the SI development status in graphs, etc. Customers (customer companies) can input "SI consultations," "QA (questions)," etc. to this device from their customer terminals. Providers (SI service providers) can obtain "SI consultations," etc. from this device. Providers can input answers to the customer's "SI consultations" and "QA" to this device from their provider terminals, and customers can obtain the answers. In addition, providers can register SI menu implementation tickets to this device and request the implementation of SI menus from this device. As a result, the purchase of SI tickets and the provision of SI services are carried out between the customer and the provider. Providers can register the ticket consumption status to this device and can also update design documents. Customers can check the progress of SI and refer to the ticket consumption status and design documents.

[0064] Next, we will explain how to generate a customer menu based on Figures 7 to 9.

[0065] Figure 7 shows an example of service list information. Service list information is generated from the "issue-implementation means correlation information" and "implementation means-SI menu correspondence information" registered by the provider in this device. As shown in the figure, the service list information first includes one or more requirement information (issues) "problems, things you want to achieve" that the customer requests, associated with the issue ID. Examples of "issues" include "I want to strengthen security" and "I want to utilize a communication platform." Next, the service list information includes the (requirement) implementation means associated with each requirement (issue). For example, if the "issue" is "strengthening security," the (requirement) implementation means may be "encryption" and "introduction of device and user authentication." Next, the service list information includes implementation methods "options that can be achieved" associated with the (requirement) implementation means. Implementation methods are marked with square boxes (checkboxes), and the user (customer) can select them by checking the boxes. An example of an implementation method "options that can be achieved" is "introduction of AAA."

[0066] Next, as shown in Figure 8, the list of services provided includes service menu information (SI menu) associated with the implementation method "Options for what can be achieved (details)," and each SI menu is assigned an SI menu ID. An example of an SI menu is "AAA service construction and implementation."

[0067] Next, as shown in Figure 9, this device generates a customer menu (menu list) for each customer from the service list information, based on customer input information that includes the information selected by the customer in the service list information (selection information). Furthermore, if the customer service information includes priority information for the services requested by the customer (prioritization information), this device refers to the priority information and generates a customer menu that includes the priority information. As shown in Figure 9, on the left side of the customer menu (menu list), the priority of each SI menu is indicated by the number of stars.

[0068] Next, the SI menu in the customer menu specifies the number of tickets (credits) for SI services. In Figure 10, for example, in the SI menu, if the SI menu ID is C001, the work details for the process "Requirements Definition," overview "Requirements Definition Document Creation," work ID "D001," and item "Hearing for Requirements Definition (Functional Requirements / Non-Functional Requirements)" include fields for "Unit Price," "Required Quantity," "Total Price," and "Credit (Ticket) Conversion." The number of tickets can be entered in the Credit (Ticket) Conversion field, and in the SI menu in Figure 10, the number of tickets is determined according to the total price of the work. There are three methods for generating tickets, for example:

[0069] (Ticket generation method 1) Method 1 involves creating tickets for each phase of the SI (system integration) process (classifying by phase). This method also allows for setting additional charges or multipliers based on response time and priority. For example, the ticket generation method for each phase might be "design phase" as "number of design document pages," "evaluation phase" as "number of test items," "construction phase" as "effort," and "inquiries" as "number of inquiries."

[0070] (Ticket generation method 2) Generation method 2 involves preparing three types of tickets (classified by content). In the following, the ticket item numbers correspond to the menu item numbers ((A) to (C)).

[0071] Ticket (prepaid) types (A) Consultation Ticket Consulting tickets are used for planning implementation solutions and consultations with consultants. For example, X yen per ticket. Tickets are consumed on an hourly basis. (B)SL (Solution) Ticket SL tickets may be common SL tickets. The number of tickets may vary depending on the implemented solution, and the content (SL) can also be changed. Ticket consumption will vary (e.g., X yen per ticket) depending on factors such as man-hours, document pages, and number of items. (C)QA Ticket For example, a Q&A ticket could be priced at X yen per ticket, and the unit price per ticket could be determined based on the duration of the Q&A session.

[0072] menu (A) Consulting Menu Consulting menu tickets are used for assessment and implementation plan creation (personnel securing), and tickets are consumed based on work time and meeting time. (B) SL Menu The unit of ticket consumption for SL menu tickets is determined by the menu item. For example, regular meetings, workshops (WS), and subcommittees are based on time; requirements definition is based on the number of pages; basic design is based on the number of pages; parameters are based on the number of items; system construction is based on the number of steps and / or construction work time; evaluation is based on the number of items and / or evaluation time; and manual creation is based on the number of pages. (C) QA Menu QA menu tickets are consumed based on the amount of work performed.

[0073] (Ticket generation method 3) Generation method 3 involves preparing only one type of common ticket for all participants.

[0074] (Ticket generation method 3-1) Method 3-1 is a method of converting all costs, such as the number of document pages and labor hours, into a common unit. For example, the unit could be defined as 1 ticket (credit or point) = A million yen or B million yen, and a standard price list could be created for each service. a) Work (build, verify, review, meetings) (Working hours * Unit price) / 1 credit (A yen) = aaa credits b) Document creation (Price per page * Number of pages) / 1 credit (B yen) = bbb credit c) education (Education cost per person * number of people) / 1 credit (A yen) = ccc credit d) Support (Unit price per hour * hour) / 1 credit (B yen) = ddd credit Manages the total number of credits (aaa + bbb + ccc + ddd).

[0075] (Ticket generation method 3-2) In ticket generation method 3-2, the unit is work time (credits are calculated based on man-hours, not cost, as in method 3-1). For example, 1 credit unit is equivalent to 1 hour.

[0076] Figures 11A and 11B illustrate the purchase and consumption of SI menu tickets. In Figures 11A and 11B, the circled "A" indicates the connection between Figures 11A and 11B via an arrow. Customers purchase tickets for the provider's SI menus through this device. Purchased tickets become eligible for SI, so the provider performs SI according to the SI menu and registers completed SI menus as completed in this device. In this device, tickets for completed SI menus are displayed as consumed tickets. In the customer ticket management information table in Figure 11B, each SI menu task ID has columns for "Number of Purchased Credits," "Number of Used Credits," and "Remaining Credits," displaying the number of credits (tickets). "Number of Used Credits" represents SI menus for which work has been completed, and "Remaining Credits" represents SI for which work has not yet been completed. These numbers allow for the management of the progress of each SI work item.

[0077] Figure 12 shows an example of how to handle situations where the remaining ticket balance is insufficient. This device manages and calculates the remaining ticket balance (starts balance calculation) based on the data in the customer ticket management information table, as well as the SI provider input information (ticket consumption information) and customer input information (purchased ticket information (quantity, purpose, etc.)), and performs a "ticket balance calculation." It then determines whether there is a "shortage" or not, and if there is a "shortage," it determines whether to "purchase or not," and if so, it returns to the "ticket balance calculation." If not, it determines whether to "allocate (transfer) tickets to other SI tickets," and if so, it returns to the "ticket balance calculation." If not, it returns to determining whether there is a "shortage" or not. If there is no shortage after determining whether there is a "shortage" or not, it "terminates."

[0078] In this embodiment, the service provider can register the number of tickets consumed and the progress status in the service management system (this device). In this embodiment, the service management system (this device) allows the service name, schedule, progress status, ticket status, etc. to be checked from a customer-specific information display screen (the screen display is provided via the web or a smart device app). In this embodiment, the service management system (this device) allows the service name, schedule, progress status, ticket status, etc. to be checked from a customer-specific information display screen (the screen display is provided via the web or a smart device app). In this embodiment, for example, tickets are pooled as a number grouped by customer, rather than by the service unit selected by the customer, and tickets that have been purchased and pooled can be added and increased at a later date. In this embodiment, SI menu tickets can be allocated (transferred or rearranged) for each service unit. In this embodiment, the allocation (work assignment) of SI menu tickets can be changed (tickets can also have an expiration date). If allocated tickets remain unused due to smooth progress, they may be returned to the pool (pool of unused tickets). If a customer requires more SI menu tickets than initially planned, they can reallocate (transfer or reassign) tickets from the pool if available, or they can change the ticket allocation from another process (another task).

[0079] [Embodiment 4] The program of this embodiment is a program that causes a computer to execute each step of the service provision support method described above. Specifically, the program of this embodiment is a program that causes a computer to execute a customer information acquisition procedure, a provider information acquisition procedure, a service ticket information generation procedure, and a service information output procedure.

[0080] The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information.

[0081] Furthermore, the program of this embodiment can also be described as a program that causes a computer to function as a procedure for acquiring customer information, acquiring provider information, generating service ticket information, and outputting service information.

[0082] The program of this embodiment can be based on the description in the service provision support device and service provision support method of the present invention. Each of the above steps can be read as, for example, "step" or "process". The program of this embodiment may also be recorded on, for example, a computer-readable recording medium. The recording medium is, for example, a non-transitory computer-readable storage medium. The recording medium is not particularly limited and includes, for example, random access memory (RAM), read-only memory (ROM), hard disk (HD), optical disk, floppy disk (FD), etc.

[0083] Although the present invention has been described above with reference to embodiments, the present invention is not limited to the above embodiments. Various modifications to the configuration and details of the present invention can be understood by those skilled in the art within the scope of the present invention.

[0084] <Note> Some or all of the above embodiments may be described as follows, but are not limited to the following: (Note 1) It includes a customer information acquisition unit, a provider information acquisition unit, a service ticket information generation unit, and a service information output unit. The aforementioned customer information acquisition unit acquires customer service information requested by the customer, The aforementioned provider information acquisition unit acquires the service information proposed by the service provider, The service ticket information generation unit generates service ticket information for each customer based on the customer service information and the provided service information. The service information output unit outputs the service ticket information, The customer information acquisition unit acquires the purchase ticket information of the customer from the service ticket information, The service information output unit outputs the purchased ticket information. Service provision support device. (Note 2) Furthermore, including the Service Provision Contracts Department, The Service Provision Contract Department generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output unit outputs contract information that includes at least one of the contract conclusion information and the contract termination information. The service provision support device described in Appendix 1. (Note 3) The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation unit generates the ticket information associated with the service menu information based on the service list information. A service provision support device as described in Appendix 1 or 2. (Note 4) Furthermore, it includes a customer menu generation unit, The customer service information includes information on the customer's selection of the options, The customer menu generation unit generates a customer menu for each customer from the service list information based on the selection information. The service provision support device described in Appendix 3. (Note 5) The customer service information includes priority information for the services requested by the customer. The customer menu generation unit generates the customer menu, which includes priority information for the service menu, based on the priority information. The service provision support device described in Appendix 4. (Note 6) The provider information acquisition unit acquires consumption ticket information relating to services for which service provision has been completed from the purchased ticket information. Furthermore, including the Services Management Department, The Service Management Department manages the progress of services provided by the provider based on the consumption ticket information. A service provision support device as described in any of the appendices 1 to 5. (Note 7) The Service Management Department, based on the Consumption Ticket Information, identifies services that have not yet been provided within the Purchase Ticket Information, and generates information on services that are currently being worked on from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output unit outputs the service information for ongoing work and the service information for services not yet started. The service provision support device described in Appendix 6. (Note 8) The Service Management Department calculates the remaining ticket balance based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket balance is insufficient to perform the services requested by the customer, it generates additional ticket information. The service information output unit outputs the ticket additional information. A service provision support device as described in Appendix 6 or 7. (Note 9) The customer information acquisition unit acquires additional purchase ticket information from the service ticket information that the customer has purchased. The service information output unit outputs the additional purchase ticket information. The service provision support device described in Appendix 8. (Note 10) The customer information acquisition unit generates transfer ticket information by reallocating the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output unit outputs the transfer ticket information. A service provision support device as described in Appendix 8 or 9. (Note 11) Furthermore, including the Service Provision Contracts Department, The Service Provision Contract Department generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output unit outputs contract information including at least one of the contract conclusion information and the contract termination information. The Service Management Department manages, based on the contract information, the orders placed by the customer for services, the acceptance of service orders by the provider, and the progress of services by the provider. A service provision support device as described in any of the appendices 6 to 10. (Note 12) The aforementioned services are services related to information system development. A service provision support device as described in any of the appendices 1 to 11. (Note 13) The provider information acquisition unit acquires the design document information for the information system development, The aforementioned Service Management Department registers and manages the aforementioned design document information, The service information output unit outputs the design document information. The service provision support device described in Appendix 12. (Note 14) This includes a customer information acquisition process, a provider information acquisition process, a service ticket information generation process, and a service information output process. The aforementioned customer information acquisition process acquires customer service information that the customer requests to be provided. The aforementioned provider information acquisition process acquires the service information proposed by the service provider, The service ticket information generation process generates service ticket information for each customer based on the customer service information and the provided service information. The service information output step outputs the service ticket information, The customer information acquisition step acquires the purchase ticket information of the customer from the service ticket information, The service information output step outputs the purchased ticket information. Methods for supporting the provision of services. (Note 15) Furthermore, including the service provision contract process, The service provision contract process generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output step outputs contract information including at least one of the contract conclusion information and the contract termination information. The method of providing services as described in Appendix 14. (Note 16) The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation process generates the ticket information associated with the service menu information based on the service list information. The method of providing services as described in Appendix 14 or 15. (Note 17) Furthermore, including the customer menu generation process, The customer service information includes information on the customer's selection of the options, The customer menu generation process generates a customer menu for each customer from the service list information based on the selection information. The method of providing services as described in Appendix 16. (Note 18) The customer service information includes priority information for the services requested by the customer. The customer menu generation process generates the customer menu, which includes priority information for the services to be provided, based on the priority information. The method of providing services as described in Appendix 17. (Note 19) The provider information acquisition step acquires consumption ticket information related to services for which service provision has been completed from the purchased ticket information, Furthermore, including the service management process, The service management process manages the progress of services provided by the provider based on the consumption ticket information. A method of providing services as described in any of the appendices 14 to 18. (Note 20) The service management process, based on the consumption ticket information, identifies services that have not yet been provided within the purchase ticket information, and generates service information for ongoing work from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output step outputs the service information for ongoing work and the service information for services not yet started. The method of providing services as described in Appendix 19. (Note 21) The service management process calculates the remaining ticket quantity based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket quantity is insufficient to perform the service requested by the customer, it generates additional ticket information. The service information output step outputs the ticket additional information. The method of providing services as described in Appendix 19 or 20. (Note 22) The customer information acquisition step acquires additional purchase ticket information of the customer that has made an additional purchase from the service ticket information, The service information output step outputs the additional purchase ticket information. The method of providing services as described in Appendix 21. (Note 23) The customer information acquisition step generates transfer ticket information by reallocating the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output step outputs the transfer ticket information. The method of providing services as described in Appendix 21 or 22. (Note 24) Furthermore, including the service provision contract process, The service provision contract process generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output step outputs contract information including at least one of the contract conclusion information and the contract termination information. The service management process manages, based on the contract information, the customer's order for services, the provider's acceptance of the service, and the provider's progress of the services. A method of providing services as described in any of the appendices 19 to 23. (Note 25) The aforementioned services are services related to information system development. A method of providing services as described in any of the appendices 14 to 24. (Note 26) The provider information acquisition step acquires the design document information for the information system development, The aforementioned service management process registers and manages the design document information, The service information output step outputs the design document information. The method of providing services as described in Appendix 25. (Note 27) This includes procedures for acquiring customer information, acquiring provider information, generating service ticket information, and outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, A program that causes a computer to perform each of the above steps. (Note 28) Furthermore, including the service provision contract procedures, The service provision contract procedure generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output procedure outputs contract information including at least one of the contract conclusion information and the contract termination information. The program described in Appendix 27. (Note 29) The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation procedure generates the ticket information associated with the service menu information based on the service list information. The program described in Appendix 27 or 28. (Note 30) Furthermore, it includes the customer menu generation procedure, The customer service information includes information on the customer's selection of the options, The customer menu generation procedure generates a customer menu for each customer from the service list information based on the selection information. The program described in Appendix 29. (Note 31) The customer service information includes priority information for the services requested by the customer. The customer menu generation procedure generates the customer menu, which includes priority information for the services to be provided, based on the priority information. The program described in Appendix 30. (Note 32) The provider information acquisition procedure acquires the consumed ticket information for services for which the service provision has been completed from the purchased ticket information, Furthermore, including service management procedures, The service management procedure manages the progress of services provided by the provider based on the consumption ticket information. The program described in any of the appendices 27 to 31. (Note 33) The service management procedure, based on the consumption ticket information, identifies services that have not yet been provided within the purchase ticket information, and generates information on services that are currently being worked on from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output procedure outputs the service information for ongoing work and the service information for services not yet started. The program described in Appendix 32. (Note 34) The service management procedure calculates the remaining ticket quantity based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket quantity is insufficient to perform the service requested by the customer, it generates additional ticket information. The service information output procedure outputs the ticket additional information. The program described in Appendix 32 or 33. (Note 35) The customer information acquisition procedure acquires additional purchase ticket information of the customer that has made an additional purchase from the service ticket information, The service information output procedure outputs the additional purchase ticket information. The program described in Appendix 34. (Note 36) The customer information acquisition procedure generates transfer ticket information by transferring the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output procedure outputs the transfer ticket information. The program described in Appendix 34 or 35. (Note 37) Furthermore, including the service provision contract procedures, The service provision contract procedure generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output procedure outputs contract information including at least one of the contract conclusion information and the contract termination information. The service management procedure manages, based on the contract information, the customer's order for services, the provider's acceptance of the service, and the provider's progress of the services. The program described in any of the appendices 27 to 36. (Note 38) The aforementioned services are services related to information system development. The program described in any of the appendices 27 to 37. (Note 39) The above provider information acquisition procedure acquires the design document information for the information system development, The aforementioned service management procedure registers and manages the design document information, The service information output procedure outputs the design document information. The program described in Appendix 38. (Note 40) This includes procedures for acquiring customer information, acquiring provider information, generating service ticket information, and outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, A computer-readable recording medium containing a program that causes a computer to perform each of the aforementioned steps. (Note 41) Furthermore, including the service provision contract procedures, The service provision contract procedure generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output procedure outputs contract information including at least one of the contract conclusion information and the contract termination information. Recording medium as described in Appendix 40. (Note 42) The aforementioned information on services provided includes information on a list of services provided. The service list information includes one or more requirement information requested by the customer, requirement implementation means associated with each requirement, implementation methods associated with the requirement implementation means, specific implementation method information with options associated with the implementation method information, and service menu information associated with the specific implementation method information. The service ticket information generation procedure generates the ticket information associated with the service menu information based on the service list information. Recording medium as described in Appendix 40 or 41. (Note 43) Furthermore, it includes the customer menu generation procedure, The customer service information includes information on the customer's selection of the options, The customer menu generation procedure generates a customer menu for each customer from the service list information based on the selection information. Recording medium as described in Appendix 42. (Note 44) The customer service information includes priority information for the services requested by the customer. The customer menu generation procedure generates the customer menu, which includes priority information for the services to be provided, based on the priority information. Recording medium as described in Appendix 43. (Note 45) The provider information acquisition procedure acquires the consumed ticket information for services for which the service provision has been completed from the purchased ticket information, Furthermore, including service management procedures, The service management procedure manages the progress of services provided by the provider based on the consumption ticket information. A recording medium as described in any of the appendices 40 to 44. (Note 46) The service management procedure, based on the consumption ticket information, identifies services that have not yet been provided within the purchase ticket information, and generates information on services that are currently being worked on from the identified services that have not yet been completed. Furthermore, unpurchased service ticket information is identified from the service ticket information and the purchased ticket information, and unstarted service information is generated from the identified unpurchased ticket information. The service information output procedure outputs the service information for ongoing work and the service information for services not yet started. Recording media as described in Appendix 45. (Note 47) The service management procedure calculates the remaining ticket quantity based on the purchased ticket information and the consumed ticket information, and if it determines that the remaining ticket quantity is insufficient to perform the service requested by the customer, it generates additional ticket information. The service information output procedure outputs the ticket additional information. Recording medium as described in Appendix 45 or 46. (Note 48) The customer information acquisition procedure acquires additional purchase ticket information of the customer that has made an additional purchase from the service ticket information, The service information output procedure outputs the additional purchase ticket information. Recording medium as described in Appendix 47. (Note 49) The customer information acquisition procedure generates transfer ticket information by transferring the purchased tickets related to the incomplete service from the purchased ticket information to the performance of the service for which the remaining tickets are insufficient. The service information output procedure outputs the transfer ticket information. Recording medium as described in Appendix 47 or 48. (Note 50) Furthermore, including the service provision contract procedures, The service provision contract procedure generates contract information indicating that a service provision contract has been concluded between the customer and the provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the aforementioned consumption ticket information, contract termination information is generated indicating that the service contract has been terminated. The service information output procedure outputs contract information including at least one of the contract conclusion information and the contract termination information. The service management procedure manages, based on the contract information, the customer's order for services, the provider's acceptance of the service, and the provider's progress of the services. A recording medium as described in any of the appendices 40 to 49. (Note 51) The aforementioned services are services related to information system development. A recording medium as described in any of the appendices 40 to 50. (Note 52) The above provider information acquisition procedure acquires the design document information for the information system development, The aforementioned service management procedure registers and manages the design document information, The service information output procedure outputs the design document information. Recording medium as described in Appendix 51. [Industrial applicability]

[0085] The present invention can be applied to various service provision fields, such as information system development (SI, etc.), consulting, search services (prior literature search, etc.), and various surveys (environmental surveys, structural deterioration surveys, maintenance inspection surveys, population surveys, health surveys, business condition surveys, etc.). [Explanation of Symbols]

[0086] 10 (10A, 10B) Service provision support device 11 Customer information acquisition department 12 Provider information acquisition department 13. Service Ticket Information Generation Department 14. Service Information Output Unit 15. Service Provision Contracts Department 16 Customer Menu Generation Unit 17. Service Management Department 101 Central Processing Unit 102 memory 103 Bus 104 Storage device 105 Input device 106 Output device 107 Communication devices

Claims

1. It includes a customer information acquisition unit, a provider information acquisition unit, a service ticket information generation unit, and a service information output unit. The aforementioned customer information acquisition unit acquires customer service information requested by the customer, The aforementioned provider information acquisition unit acquires the service information proposed by the service provider, The service ticket information generation unit generates service ticket information for each customer based on the customer service information and the provided service information. The service information output unit outputs the service ticket information, The customer information acquisition unit acquires the purchase ticket information of the customer from the service ticket information, The service information output unit outputs the purchased ticket information. Service provision support device.

2. Furthermore, including the Service Provision Contracts Department, The Service Provision Contract Department generates contract information indicating that a service provision contract has been concluded between the customer and the service provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the contract for the said service has ended. The service information output unit outputs contract information that includes at least one of the contract conclusion information and the contract termination information. The service provision support device according to claim 1.

3. The aforementioned services are services related to information system development. The service provision support device according to claim 1 or 2.

4. Including a service management department, The provider information acquisition unit acquires the design document information for the information system development, The aforementioned service management department registers and manages the aforementioned design document information, The service information output unit outputs the design document information. The service provision support device according to claim 3.

5. This includes a customer information acquisition process, a provider information acquisition process, a service ticket information generation process, and a service information output process. The aforementioned customer information acquisition process acquires customer service information that the customer requests to be provided. The aforementioned provider information acquisition process acquires the service information proposed by the service provider, The service ticket information generation process generates service ticket information for each customer based on the customer service information and the provided service information. The service information output step outputs the service ticket information, The customer information acquisition step acquires the purchase ticket information of the customer from the service ticket information, The service information output step outputs the purchased ticket information. A service provision support method in which each process is executed by computer.

6. This includes procedures for acquiring customer information, acquiring provider information, generating service ticket information, and outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, A program that causes a computer to perform each of the above steps.

7. Furthermore, including the service provision contract procedures, The service provision contract procedure generates contract information indicating that a service provision contract has been concluded between the customer and the service provider regarding the provision of services related to the purchased service ticket, based on the purchased ticket information. Furthermore, based on the consumption ticket information for services whose provision has been completed within the purchased ticket information, contract termination information is generated indicating that the contract for the said service has ended. The service information output procedure outputs contract information including at least one of the contract conclusion information and the contract termination information. The program according to claim 6.

8. The aforementioned services are services related to information system development. The program according to claim 6 or 7.

9. Includes a service management procedure, The above provider information acquisition procedure acquires the design document information for the information system development, The aforementioned service management procedure registers and manages the design document information, The service information output procedure outputs the design document information. The program according to claim 8.

10. This includes procedures for acquiring customer information, acquiring provider information, generating service ticket information, and outputting service information. The aforementioned customer information acquisition procedure acquires customer service information that the customer requests to be provided, The aforementioned provider information acquisition procedure acquires the service information proposed by the service provider, The service ticket information generation procedure generates service ticket information for each customer based on the customer service information and the provided service information. The service information output procedure outputs the service ticket information, The customer information acquisition procedure acquires the purchase ticket information of the customer from the service ticket information, The service information output procedure outputs the purchased ticket information, A computer-readable recording medium containing a program that causes a computer to perform each of the aforementioned steps.

Images