JP4865591B2 - Service management system, service management method, and service management program - Google Patents

Description

  The present invention relates to a service management system, a service management method, and a service management program in an application service provider.

  With the development of the Internet, companies and individuals create and publish web pages. In a company, publishing a web page on a network may lead to sales promotion of products and improvement of customer satisfaction. However, for companies that do not have a system administrator, creating and maintaining web pages is cumbersome. In such a case, an application service provider may be used.

A technology related to a web page that can efficiently update a web page using this application service provider is disclosed (for example, see Patent Document 1). In Patent Document 1, the management computer records the publication information in the storage means in association with the publication time. When the release time comes, the management computer generates a web page using the posting information associated with the release time and the template, and records it in the web page storage means. Thereby, since web page data is automatically created at the time of publication, hardware resources can be used effectively.
Japanese Patent Laying-Open No. 2005-182160 (FIGS. 3 to 5)

  By the way, in a company using an application service provider, there are cases where the application service provider manages transaction information with customers. In this case, the application service provider needs to acquire transaction information after identifying which company the customer is. In addition, the acquired transaction information has to be managed in association with each company. For this reason, the acquisition and management of transaction information has been complicated in the application service provider.

  The present invention has been made in view of the above-described problems, and an object thereof is service management capable of efficiently acquiring and efficiently managing data related to a second customer who is a customer of a first customer who uses an application service provider. A system, a service management method, and a service management program are provided.

In order to solve the above problem, the invention according to claim 1 is characterized in that a first customer ID for identifying a first customer and a second customer ID for identifying a second customer that is a customer of the first customer. Transaction data storage means for associating a transaction ID for identifying a transaction between the first customer and the second customer, and storing transaction information including information related to the progress of the transaction, and the transaction ID First mail address data storage means for recording the associated reception mail address; and portal information storage means for recording each status of the distribution state name of the transaction used by the first customer in association with the first customer ID. If, first and second mail address data storage means for recording the status by email address for each of the transaction ID and status, the first client terminal and the second customer the first customer use used A service management system comprising a control unit connected to a customer terminal via a network, providing the transaction information to a second customer, and managing a screen dedicated to the first customer used by the first customer, wherein the control Obtains information related to the transaction with the second customer via the first customer dedicated screen of the first customer terminal, assigns the transaction ID, the transaction ID, the first customer ID, the second customer the information on transactions with that recorded in the data storage means and the transaction ID assigning means, said grant acceptance mail address for transaction ID, reception mail address assignment means for recording the first email address data storing means When each stearyl using the transaction information and the reception mail address, and accepting mail address output means for outputting via the first customer-specific screen, the transaction by the first customer ID The status information is specified in the portal information storage means, a status-specific mail address is assigned to each status, and the status-specific mail address assignment means is recorded in the second mail address data storage means in association with the transaction ID of this transaction. And a status-specific e-mail address output means for outputting the status-specific e-mail address associated with the transaction information via the first customer dedicated screen, and an e-mail from the second customer terminal to the received e-mail address. The second customer e-mail address registration means for recording the e-mail address of the sender that sent the e-mail in the transaction data storage means as the e-mail address of the second customer associated with the transaction ID. and, in the case of receiving the e-mail for the previous Symbol state-specific e-mail address, this state by e-mail Identify the status and the transaction ID associated with the address, the progress of the transaction specified by the transaction ID, the progress updating means for updating the status of the transaction identified from the state-specific email address, the second A means for sending a notification to the second customer that the situation has been changed to the email address of the second customer recorded in the transaction data storage means when the progress status of the customer transaction is changed; This is the summary.

The invention according to claim 2, the service management system according to claim 1, wherein the first
A dedicated site data storage means for storing the first customer dedicated screen data of the first customer in association with the customer ID is further provided, and the control unit includes a first customer ID and a transaction ID from the second customer terminal. An access request accepting means for receiving an access request; first customer dedicated screen data corresponding to a first customer ID included in the access request is acquired from the dedicated site data storage means; and the transaction ID included in the access request Data acquisition means for acquiring the transaction information according to the transaction data storage means, and generating the information providing screen data for the second customer by incorporating the acquired transaction information into the first customer dedicated screen data The present invention further includes an information providing means for transmitting to the second customer terminal.

According to a third aspect of the present invention, the service management system according to the second aspect further comprises a template storage means for storing a template for each subversion in order to create the first customer dedicated screen data of the first customer. In the template, a distribution pattern selection pattern used in a portal site generated using the sub-version template is recorded, and the control unit receives the first customer from the first customer terminal. Data for specifying a subversion to be used is acquired, a template selection unit that acquires a template corresponding to the subversion from the template storage unit, and the first customer-specific screen data is generated based on the acquired template, and the dedicated a dedicated screen generation means for storing the site data storage means, said first When receiving data for specifying a distribution state name pattern from a customer terminal, the distribution state name corresponding to the selected distribution state name pattern is acquired from the specified template data, The gist further includes a means for recording the information in the portal information storage means in association with the first customer ID of the first customer .

The invention according to claim 4 is a first customer ID for identifying a first customer, a second customer ID for identifying a second customer who is a customer of the first customer, the first customer, and the first customer. (2) Transaction data storage means for storing transaction information including information related to the progress of the transaction in association with a transaction ID for specifying a transaction with a customer, and a reception e-mail address associated with the transaction ID a first e-mail address data storing means, in association with the first customer ID, and the portal information storage means for each status of the distribution state names of transactions which the first customer uses are recorded, for each of the transaction ID and status A second e-mail address data storage unit that records e-mail addresses according to status, a first customer terminal used by the first customer, and a second customer terminal used by the second customer via a network And a control unit connected Te, provide the transaction information to the second customer, a service managing method of managing a first customer-specific screen the first customer uses, the control section, the first customer Obtain information related to the transaction with the second customer via the screen for exclusive use of the first customer of the terminal, give a transaction ID, and provide information related to the transaction with the transaction ID, the first customer ID, and the second customer. a transaction ID assigning step of recording said transaction data storage means, by giving the acceptance mail address for the transaction ID, and the accepted e-mail address allocation step of recording the first email address data storage means, said transaction information and the receiving e-mail address, the accepting email address output step of outputting through the first customer-specific screen, the first customer ID in the portal information storage means each status using the transaction Identify Oite, by applying a state-specific email address for each status, a status by email imparting step of recording said second e-mail address data storing means in association with the transaction ID of the transaction, the transaction information
A state-specific e-mail address output stage for outputting the state-specific e-mail address associated with the information via the first customer dedicated screen, and an e-mail received from the second customer terminal for the received e-mail address to the source of the email address that sent the e-mail, and a second customer mail address registration step of recording said transaction data storage means as said second customer email address associated with the transaction ID, before Symbol When an e-mail is received for a state-specific e-mail address, the status associated with this state-specific e-mail address and the transaction ID are specified, and the progress of the transaction specified by the transaction ID is determined for each state. and a progress update stage to be updated on the status of transactions that were identified from the e-mail address, related to transactions of the second customer If Hakado situation has changed, the gist to perform the step of transmitting a notification that situation against the second customer is changed, the e-mail address of the second customer recorded in the transaction data storage means And

The invention according to claim 5 is a first customer ID for specifying a first customer, a second customer ID for specifying a second customer that is a customer of the first customer, the first customer, and the first customer. (2) Transaction data storage means for storing transaction information including information related to the progress of the transaction in association with a transaction ID for specifying a transaction with a customer, and a reception e-mail address associated with the transaction ID a first e-mail address data storing means, in association with the first customer ID, and the portal information storage means for each status of the distribution state names of transactions which the first customer uses are recorded, for each of the transaction ID and status A second e-mail address data storage unit that records e-mail addresses according to status, a first customer terminal used by the first customer, and a second customer terminal used by the second customer via a network And a control unit connected Te, provide the transaction information to the second customer, a service management program for managing the first customer-specific screen the first customer use, the control unit, the first customer Obtain information related to the transaction with the second customer via the screen for exclusive use of the first customer of the terminal, give a transaction ID, and provide information related to the transaction with the transaction ID, the first customer ID, and the second customer. The transaction ID assigning means for recording in the transaction data storage means, the acceptance mail address for the transaction ID , and the receipt mail address giving means for recording in the first mail address data storage means, with the first customer ID Each status used for the transaction is specified in the portal information storage means, a status-specific mail address is assigned to each status, and the second information is associated with the transaction ID of the transaction. -Mail address data storing means state by mail addressing means for recording in said transaction said state-specific email address associated with the information, the first state by email address output means for outputting through a customer-specific screen, the receiving mail When an e-mail is received from the second customer terminal for the address, the transaction data is used as the e-mail address of the second customer associated with the transaction ID, using the e-mail address of the sender that transmitted the e-mail the second customer mail address registration means for recording in the storage means, when receiving an e-mail for pre SL state by email address, to identify the status and the transaction ID associated with this state per e-mail address, this The progress of the transaction specified by the transaction ID is shown for the transaction specified from the state-specific e-mail address . When the progress status update means for updating to the status and the progress status regarding the second customer are changed, a notification that the status has been changed for the transaction of the second customer is recorded in the transaction data storage means. The gist is to make it function as means for transmitting to the mail address of the second customer .

(Function)
According to the present invention , the control unit acquires information about the second customer ID and the transaction via the first customer dedicated screen, assigns a transaction ID, and associates the transaction data with the first customer ID. Record in storage means. The control unit assigns a reception mail address in association with the transaction ID, records it in the first mail address data storage means, and outputs the transaction information and the reception mail address via the first customer terminal. When the control unit receives an e-mail from the second customer terminal with respect to the reception e-mail address, the e-mail address of the transmission source that has transmitted the e-mail is used as the e-mail address of the second customer associated with the transaction ID. Record in the transaction data storage means. For this reason, a control part can acquire a 2nd customer's e-mail address efficiently via the reception e-mail address linked | related with transaction information, and can be linked | related and recorded more reliably to corresponding transaction information. Therefore, it is possible to efficiently acquire the email address of the second customer who is the customer of the first customer and efficiently manage it in association with the transaction information associated with the first customer. Further, the second customer can register a mail address with a simple operation of sending an e-mail.

According to the present invention , the control unit acquires the status of the first customer ID associated with the transaction information acquired via the first customer dedicated screen from the status data storage unit, and classified by status corresponding to each status E-mail addresses are assigned, and these e-mail addresses are recorded in the second e-mail address data storage means in association with the transaction ID. The control unit outputs the transaction information and the state-specific e-mail address via the first customer dedicated screen. Furthermore, when the control unit receives an e-mail for the state-specific e-mail address, the control unit specifies the status and the transaction ID associated with the state-specific e-mail address, and the progress of the transaction specified by the transaction ID The status is updated to the status specified from the state-specific mail address. For this reason, the progress of the transaction can be efficiently updated based on the mail address according to the state of the received mail.

According to the present invention , the control unit obtains the first customer dedicated screen data corresponding to the first customer ID included in the access request from the second customer terminal from the dedicated site data storage means, and is included in the access request. The transaction information corresponding to the transaction ID is acquired from the transaction data storage means. The control unit generates the information providing screen data for the second customer by incorporating the acquired transaction information into the first customer dedicated screen data, and transmits the information providing screen data to the second customer terminal. For this reason, the control unit can provide transaction information including the progress of the transaction to the corresponding secondary customer.

According to this invention , a control part acquires the data which specify the subversion which a 1st customer uses from a 1st customer terminal, and acquires the template corresponding to this subversion from the said template memory | storage means. A control part produces | generates the said 1st customer exclusive screen data based on the acquired template, and memorize | stores it in the said exclusive site data storage means. For this reason, since the 1st customer exclusive screen data can be produced | generated, using the template corresponding to a primary customer, the portal site suitable for a primary customer can be produced | generated efficiently.

  ADVANTAGE OF THE INVENTION According to this invention, the data regarding the 2nd customer who is a customer of the 1st customer who uses an application service provider can be acquired efficiently, and can be managed efficiently.

  Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS. In this embodiment, a system for managing an ASP service will be described. Here, the first customer who uses this ASP service is called a primary customer. And the 2nd customer (namely, customer of a primary customer) using the service which a primary customer provides using this system is called a secondary customer.

  As shown in FIG. 1, the ASP system 10 in this embodiment includes a web server 15 and an ASP service engine 20. The web server 15 is connected to a primary customer terminal 51 used by a primary customer and a secondary customer terminal 55 used by a secondary customer via a network.

  The primary customer terminal 51 and the secondary customer terminal 55 are provided with a display, a keyboard, and a pointing device. Furthermore, each terminal has a built-in browser program, can display screen data described in a predetermined language (for example, HTML) on a display, and can transmit the data input to this screen.

The primary customer terminal 51 is used when setting the portal site of the primary customer. The primary customer terminal 51 functions as a first customer terminal and is connected to the printer 52.
The secondary customer terminal 55 is used when displaying a portal site or setting data such as a password via a browser.

  The ASP service engine 20 of the ASP system 10 is also connected to the primary customer terminal 51 and the secondary customer terminal 55 via the network. The ASP service engine 20 performs user authentication using data received via the web server 15 and directly transmits / receives data to / from the primary customer terminal 51 and the secondary customer terminal 55 that have been authenticated by the user.

Further, the ASP service engine 20 is connected to a secondary customer mobile terminal 56 carried by the secondary customer via a network. In the present embodiment, the secondary customer mobile terminal 56 is, for example, a mobile phone terminal having a two-dimensional code reading function and a mail function. The ASP service engine 20 acquires a mail address from the secondary customer portable terminal 56 and transmits a message to the mail address. Further, the ASP service engine 20 receives a mail from a two-dimensional code reading terminal (not shown) used by the primary customer via the network. The secondary customer terminal 55 and the secondary customer portable terminal 56 function as a second customer terminal.

The ASP service engine 20 includes a control unit 21, a template database 22, a portal information database 24, and a physical distribution information database 26.
The control unit 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing to be described later. This process includes a transaction ID assigning stage, a reception mail address assignment stage, a reception mail address output stage, a second customer mail address registration stage, a state-specific mail address assignment stage, a state-specific mail address output stage, and a progress update stage. , An access request acceptance stage, a data acquisition stage, an information provision stage, a template selection stage, a dedicated screen generation stage, and the like. Then, by executing the service management program for this purpose, the control unit 21 causes the transaction ID giving means, the received mail address giving means, the received mail address output means, the second customer mail address registering means, the state-specific mail address giving means. It functions as a state-specific mail address output means. Further, the control unit 21 functions as a progress status update unit, an access request reception unit, a data acquisition unit, an information provision unit, a template selection unit, a dedicated screen generation unit, and the like. The control unit 21 is connected to the template database 22, the portal information database 24 and the physical distribution information database 26.

  The template database 22 functions as a template storage unit. In the template database 22, template data 220 is recorded as shown in FIG. The template data 220 is template data that can be used for general purposes used by a primary customer to set up a portal site. An initial value is assigned to an item set using the template data 220. This initial value can be changed by the user (primary customer). This template data 220 is registered before a contract with the primary customer is made. The template data 220 includes data related to the subversion identifier, login definition, distribution name definition, quantity definition, distribution state selection definition, print item definition, and standard function.

  In the subversion identifier data area, identifier data for specifying the subversion of the template is recorded. In order to simplify the description, in the present embodiment, it is assumed that three subversions for “service inquiry system”, “vacant seat reservation system”, and “distribution tracking system” are used.

  In the login definition data area, data for defining a login process in the portal site generated by using this sub-version template is recorded. Specifically, data for specifying the type of data used when specifying the secondary customer at the time of login and data for selecting whether or not there is a password at the time of login are recorded. In this embodiment, in order to specify a secondary customer, a site sub ID is selected as described later in the login definition. When “with password” is selected, the generated portal site is configured to activate the password verification function program and execute the authentication process.

  In the distribution name definition data area, a method for determining the name of the distribution (object to be traded between the primary customer and the secondary customer) in the portal site generated using the template of this subversion is specified. Data is recorded. Specifically, in this distribution name definition data area, “input of distribution name” or “selection of distribution name” can be selected as a name determination method. Furthermore, for “select logistics name”, an identifier for specifying a logistics name selection pattern and a field for setting a logistics name that can be selected in each selection pattern are provided.

  Specifically, “input” is set in the sub-version of “distribution tracking system”. In the sub-version of “vacant seat reservation system”, “selection” is set. In this case, a plurality of distribution names and a pattern identifier composed of these distribution names are recorded in this data area. For example, the sub-version of “vacant seat reservation system” includes a first pattern composed of four logistics names “counter”, “non-smoking seat table”, “smoking seat table”, and “tatami room”, “counter”, “ There is a second pattern composed of five logistics names: “two seats”, “four seats”, “six seats”, and “tatami room”. In this case, each physical distribution name and the pattern identifier are recorded in association with each other.

  In the quantity definition data area, data for setting the type of quantity used in the distribution in the portal site generated using the subversion template is recorded. In the present embodiment, it is possible to specify whether one type or two types of quantities are used, and therefore data for specifying the type of the quantity is recorded in this data area. For example, in the sub version for “service inquiry system” and “distribution tracking system”, there is one distribution, so one kind of quantity is selected. In the sub-version for the “vacant seat reservation system”, “adult” and “child” are handled as different quantities, so two kinds of quantities are selected.

  The logistics status selection definition data area associates data for specifying a logistics status selection pattern used in a portal site generated using this subversion template with data relating to the logistics status name used in each pattern. Has been recorded. For example, in the sub-version for “vacant seat reservation system”, there are six first selection patterns of “meeting”, “sixth”, “third”, “guidance”, “completion”, and “cancellation”. Logistics state name is recorded. In addition, as the second selection pattern, six logistics state names of “Meeting”, “15 minutes ago”, “5 minutes ago”, “Guidance”, “Completed”, and “Cancel” are recorded. As the selection pattern, five logistics names of “waiting for vacant seat”, “acceptable”, “guidance”, “complete”, and “cancel” are recorded.

  In the print item definition data area, data for specifying an item to be printed in a portal site generated using the subversion template is recorded. In the print item definition data area, data for specifying an item to be output as a two-dimensional code when a two-dimensional code is printed is also recorded.

  In the standard function data area, data for specifying a function program to be implemented as a standard function in the portal site generated using the subversion template is recorded. This function program includes a password audit function program, a status notification function program, a distribution status change function program, and the like.

  Here, the password audit function program is a program that prompts the user to register a password at the first access from the secondary customer terminal 55, prompts the user to input the password at the second and subsequent accesses, and performs user authentication using this password. . The data for specifying the password audit function is recorded in the sub-version standard function data area defined as “password present” in the login definition data.

  The status notification function program is a program for notifying the secondary customer every time the current status is updated. In the present embodiment, the data specifying the status notification function is recorded in the standard function data area of the subversion for the “vacant seat reservation system”.

The distribution status change function program is a program for acquiring a change in distribution status using an email address. In the present embodiment, the data specifying the distribution status change function is recorded in the subversion standard function data area for the “distribution tracking system”.

  On the other hand, the portal information database 24 functions as dedicated site data storage means. As shown in FIG. 3, portal information data 240 related to the portal site of the primary customer set using the template data 220 is recorded in the portal information database 24. The portal information data 240 functions as first customer-specific screen data for each primary customer and is registered in a portal setting process described later. The portal information data 240 includes site ID, primary customer name, login definition, logistics name definition, quantity definition, logistics status name, print item, standard function, secondary customer unique ID definition, extended function, item name and print. Contains data about the title name. Note that data relating to login definition, distribution name definition, quantity definition, distribution state name, print item, and standard function is set based on sub-version template data 220 used by the primary customer.

  In the site ID data area, a site ID for specifying the portal site of the primary customer is recorded. Since the primary customer can be specified by this site ID, the site ID also functions as a first customer ID for specifying the primary customer. In the present embodiment, a URL (Uniform Resource Locator) is used as the site ID.

Data relating to the name of the primary customer is recorded in the primary customer name data area.
In the login definition data area, data related to the login definition used by the primary customer is recorded.

In the distribution name definition data area, a method for determining the name of the distribution used by the primary customer or data relating to the distribution name used is recorded.
Data relating to the type of quantity used by the primary customer is recorded in the quantity definition data area.

In the distribution status name data area, data relating to the distribution status used by the primary customer is recorded.
In the print item data area, data for specifying an item to be printed by the primary customer is recorded.

In the standard function data area, data for specifying a function program to be implemented as a standard function in the sub version used by the primary customer is recorded.
In the secondary customer unique ID definition data area, the type of data used as an identifier (second customer ID) unique to the secondary customer for specifying the secondary customer in the primary customer is recorded. As the data type, there are a secondary customer's telephone number, e-mail address or arbitrary password, and data specifying any of these is recorded in the secondary customer unique ID definition data.

In the extended function data area, data related to the extended function program individually added to the primary customer is recorded.
In the item name data area, data relating to the item name used as the title of each data by the primary customer is recorded. This item name is recorded in association with the corresponding data. For example, FIG. 9 shows a data layout diagram 600 that displays the positions where each data item is placed. A corresponding item name is displayed in “XXX” of the data layout diagram 600. For example, for the “site sub ID” data, “reservation number” is recorded as the item name in the portal information data 240 of the primary customer who provides the service using the information provision screen 610 of FIG. The item name to be set includes a site sub ID, a secondary customer unique ID, a reception date, a secondary customer name, a distribution name, a first type quantity, a second type quantity, a delivery date, and a name related to the current situation. For example, in the information provision screen 610 of FIG. 10, “reservation number” as the item name of the site sub ID, “password” as the secondary customer unique ID, “reservation date” as the reception date, and “reservation date” as the secondary customer name. “Customer name”, “reservation target name” as the logistics name, “status” as the item name of the current status, and the like are set.

In the print title name data area, data relating to the title name of the physical distribution slip to be printed is recorded. For example, print title names include “reservation slip” and “numbered ticket”.
The logistics information database 26 functions as transaction data storage means, first mail address data storage means, status data storage means, and second mail address data storage means. In this physical distribution information database 26, physical distribution information data 260 relating to physical distribution (transaction information) provided by the primary customer to the secondary customer is recorded as shown in FIG. This physical distribution information data 260 is recorded when an application for service provision is made by a secondary customer. The distribution information data 260 includes a site ID, a site sub ID, a secondary customer name, a distribution name, a reception date, a first type quantity, a second type quantity, a delivery date, a current situation, a customer email address, a telephone number, a password, Data on the reception e-mail address and the e-mail address by physical distribution state associated with each status are included. Note that the items shown in parentheses in FIG. 4 (second-class quantity, delivery date, telephone number, password, mail address and status according to logistics status) depend on the subversion used by the primary customer. It may not be included in the data.

  In the site ID data area, site ID data that functions as an identifier for identifying the primary customer is recorded. In the present embodiment, the URL of the portal site of the primary customer is used as the site ID. The distribution information data 260 and the portal information data 240 are associated with each other through the site ID.

  In the site sub ID data area, a site sub ID for identifying each physical distribution information data 260 is recorded. The site sub ID is an identifier (transaction ID) for specifying each service request received from the secondary customer by the primary customer.

Data relating to the name of the secondary customer is recorded in the secondary customer name data area.
In the distribution name data area, data relating to a name for specifying the distribution (object to be traded between the primary customer and the secondary customer) is recorded. This physical distribution name may be directly input and recorded, or may be selected from physical distribution names associated with the selection pattern of the sub-version physical distribution name definition data. Specifically, in the case of the “service inquiry system”, data relating to the name to be inquired, and in the case of the “vacant seat inquiry system”, data relating to the name for specifying the reserved seat are recorded.

In the reception date data area, data relating to the date on which a service request from a secondary customer is received is recorded.
In the first type quantity data area, data relating to the first type quantity relating to this service request is recorded.

  In the second type quantity data area, data relating to the second type quantity relating to this service request is recorded. This second quantity data area is used only when the quantity definition is “two types” in the subversion used by the primary customer. For example, in the “vacancy reservation system”, when the first type quantity is “adult” and the second type quantity is “child”, the number of adults is recorded in the first type quantity data area, and the second type quantity is recorded. The number of children is recorded in the data area.

In the delivery date data area, data related to the delivery date for the secondary customer is recorded. This delivery date data is recorded only when a delivery date is set between the primary customer and the secondary customer.
In the current status data area, data relating to the current status (status) of the service for the secondary customer is recorded.

In the customer mail address data area, the mail address of the secondary customer is recorded.
Data relating to the telephone number of the secondary customer is recorded in the telephone number data area.
Data related to the password set by the secondary customer is recorded in the password data area. This password data area is used only when the login definition of the sub version used by the primary customer is “with password”.

In the reception mail address data area, a mail address (reception mail address) for receiving a mail from the secondary customer is recorded.
The distribution state-specific mail address data area stores the distribution state-specific mail address. This mail address for each physical distribution state is an e-mail address set in correspondence with the physical distribution state. This distribution state-specific e-mail address is used only when the distribution status change function is used.

  Processing in the ASP system 10 described above will be described with reference to FIGS. Here, portal setting processing for setting the portal site of the primary customer will be described first.

(Portal setting process)
First, processing for setting a portal site of a primary customer will be described with reference to FIG.
In this process, the control unit 21 of the ASP service engine 20 acquires information about the primary customer from the primary customer terminal 51 (step S1-1). Specifically, first, the primary customer causes the primary customer terminal 51 to access the ASP system 10 to display a portal site setting screen. Next, using this setting screen, data relating to the primary customer including the primary customer name is input. Then, by instructing registration, the primary customer terminal 51 transmits the input data relating to the primary customer to the ASP system 10. The control unit 21 of the ASP service engine 20 of the ASP system 10 creates portal information data 240 including the received primary customer name.

  Next, the control unit 21 performs subversion selection processing (step S1-2). Specifically, the control unit 21 transmits information regarding each definition and standard function of the subversion to the primary customer terminal 51 in order to select the subversion. In the primary customer terminal 51, a subversion is selected from each definition and standard function corresponding to the business form of the primary customer. Then, by instructing registration, the primary customer terminal 51 transmits the input sub-version identifier data to the ASP system 10. The control unit 21 of the ASP service engine 20 of the ASP system 10 acquires the template data 220 corresponding to the received subversion identifier from the template database 22. The control unit 21 extracts the login definition, quantity definition, print item definition, and standard function definition data of the acquired template data 220, and creates the login definition data area, quantity definition data area, print item data of the created portal information data 240. It records in each of the area and the standard function data area.

  Here, the control part 21 performs the setting process of the selection data in the acquired template (step S1-3). Here, the control part 21 produces | generates the setting screen for a primary customer to set. Specifically, the control unit 21 acquires the template data 220 of the selected subversion, and extracts a selection pattern and each distribution state name corresponding thereto from the distribution state selection definition data of the template data 220. The control unit 21 generates a setting screen including the extracted selection pattern and each physical distribution state name corresponding thereto. Further, the control unit 21 includes a plurality of distribution state name setting fields for setting a distribution state name selection pattern in the setting screen.

  Furthermore, the control unit 21 determines whether the distribution name definition of the acquired template is “selection” or “input”. Here, when the distribution name is “selection”, the selection pattern of the distribution name definition data and each distribution name corresponding thereto are extracted. The control unit 21 includes the extracted selection pattern and each physical distribution name corresponding thereto in the setting screen. Further, the control unit 21 includes a plurality of distribution name setting fields for setting a distribution name selection pattern in the setting screen.

  In addition, the control unit 21 determines whether the login definition data of the acquired template data 220 is “with password” or “without password”. Here, when the login definition is “having a password”, information for selecting a type for specifying the secondary customer unique ID is included in the setting screen.

  Then, the control unit 21 transmits the generated setting screen data to the primary customer terminal 51. The primary customer terminal 51 displays a setting screen based on the received data. On this setting screen, the distribution state name is displayed for each pattern. In this setting screen, the primary customer selects a distribution state name pattern with reference to the distribution state name. Here, when there is no selected distribution state name or when it is desired to set a unique distribution state name, the primary customer inputs an arbitrary distribution state name in the distribution state name setting field.

  When the distribution name is displayed for each pattern on the setting screen, the primary customer refers to the distribution name and selects the distribution name pattern. Here, when there is no selected distribution name or when it is desired to set a unique distribution name, the primary customer inputs an arbitrary distribution name in the distribution name setting field.

  Furthermore, when the secondary customer's e-mail address, telephone number or password is displayed on this setting screen as the type for identifying the secondary customer unique ID, the primary customer selects one of these types. To do.

  Then, when the primary customer instructs registration, the primary customer terminal 51 determines the selected pattern, the distribution state name or distribution name input in the setting field, and the type for specifying the secondary customer unique ID. Is transmitted to the ASP system 10. The control unit 21 of the ASP service engine 20 acquires data corresponding to the received data from the template database 22 and records it in the portal information data 240. Specifically, when receiving data for specifying a distribution state name pattern, the control unit 21 corresponds to the selected distribution state name pattern from the template data 220 of the selected subversion identifier. Each distribution status name to be acquired is acquired and recorded in the distribution status name data area of the portal information data 240. Further, when receiving the distribution state name data input in the distribution state name setting field, the control unit 21 records the acquired distribution state name in the distribution state name data area of the portal information data 240.

  Further, when receiving data for specifying a distribution name pattern, the control unit 21 acquires each distribution name corresponding to the selected distribution name pattern from the specified template data 220, and Recorded in the logistics name data area of the portal information data 240. Further, when receiving the distribution name data input in the distribution name setting field, the control unit 21 records the acquired distribution name in the distribution name data area of the portal information data 240.

Further, when receiving the type for specifying the secondary customer unique ID, the control unit 21 records it in the secondary customer unique ID definition data area of the same portal information data 240.
Furthermore, the control part 21 sets an extended function with respect to the portal site of a primary customer (step S1-4). Specifically, when adding an extended function individually, the extended function program data is acquired from the primary customer terminal 51 and recorded in the extended function data area of the portal information data 240 of the primary customer.

  Next, the control unit 21 executes setting processing for each item name and print title name (step S1-5). Here, the control unit 21 transmits, to the primary customer terminal 51, data of a setting screen for prompting input of item data used by the primary customer and a print title name. The primary customer terminal 51 displays a setting screen based on the received data. This setting screen includes an item name input column and a print title input column corresponding to item data (distribution name, first type quantity, current status, etc.) used by the primary customer. In this setting screen, the primary customer inputs an item name and a print title in each input field. Then, by instructing registration, the primary customer terminal 51 transmits the input name and print title name of each item to the ASP system 10. The control unit 21 of the ASP service engine 20 records the item name associated with each data item in the item name data area of the portal information data 240 and records the print title name in the print title name data area.

  Next, the control unit 21 executes portal site registration processing (step S1-6). Specifically, the control unit 21 first assigns and records a URL to the portal information data 240 set in steps S1-1 to S1-5. Further, the control unit 21 generates a portal site of each primary customer associated with the assigned URL and records it on the web server 15.

Then, using the portal site set in this way, the primary customer provides a service to the secondary customer.
Next, processing during provision of this service will be described. Here, description will be made in the order of secondary customer use application processing, secondary customer mail address acquisition processing, status browsing processing, physical distribution status acquisition processing, and notification processing.

(Secondary customer usage application processing)
The secondary customer use application process shown in FIG. 6 is executed when the secondary customer applies for service use to the primary customer. In this case, the secondary customer provides the primary customer with the content of using the service of the primary customer and the entry content including information on the secondary customer. In the case of book reservation, the contents of this entry include the book name, quantity, and delivery date to be reserved. In addition, the entry contents include a desired seat and the number of people in the case of waiting for a vacant seat of a customer visiting the store. Further, in the case of a delivery service, the entry content includes the name, number, delivery destination, and delivery date of items to be sent. The information about the secondary customer includes the name and telephone number of the secondary customer.

  The primary customer who received the provision from the secondary customer causes the primary customer terminal 51 to access the ASP system 10. In this case, after user authentication, the control unit 21 executes secondary customer application registration processing (step S2-1). Specifically, the control unit 21 transmits a distribution information data registration screen to the primary customer terminal 51. In this case, since the entry contents to be acquired differ depending on the subversion used by the primary customer, a registration screen corresponding to this subversion is transmitted. The primary customer inputs the entry contents and information about the secondary customer to the primary customer terminal 51 and instructs registration. The primary customer terminal 51 transmits the entered entry content and information about the secondary customer to the ASP system 10.

  As a result, the control unit 21 of the ASP system 10 acquires the entry content and information about the secondary customer and records the information as the distribution information data 260 in the distribution information database 26. Further, the control unit 21 records the site ID of the primary customer specified by the user authentication in the physical distribution information database 26. Further, the control unit 21 records the current date as the reception date in the reception date data area.

Next, the control part 21 performs the setting process of a site sub ID and a reception mail address (step S2-2). Specifically, the control unit 21 assigns a site sub ID to the registered physical distribution information data 260 and records it in the physical distribution information database 26. Further, the control unit 21 adds a checksum for the site ID and the site sub ID to the site ID and the site sub ID, and generates a reception mail address having a character string and a numerical sequence obtained by encrypting these. Then, the generated reception mail address is recorded in the reception mail address data area of the physical distribution information data 260.

  Then, it is determined whether or not there is a distribution status change function as a standard function of the sub-version of the primary customer (step S2-3). Specifically, the control unit 21 extracts portal information data 240 associated with the site ID recorded in the physical distribution information database 26. Further, the control unit 21 determines whether the standard function of the template data 220 specified by the subversion identifier recorded in the extracted portal information data 240 includes data specifying the distribution status change function.

  In this case, when data specifying the distribution status change function is recorded (in the case of “YES” in step S2-3), the distribution state-specific mail address setting process is executed (step S2-4). Specifically, first, the control unit 21 acquires the distribution state name data recorded in the extracted portal information data 240. Furthermore, the control unit 21 assigns an e-mail address that is not used in the other physical distribution information data 260 to each status of the acquired physical distribution state name. Then, each status and the corresponding mail address are associated with each other and registered in the distribution information data 260.

  Next, the control unit 21 executes a distribution slip output process (step S2-5). Specifically, the control unit 21 acquires a subversion identifier included in the portal information data 240 of the primary customer, and acquires print item definition data associated with the subversion identifier from the template database 22. The control unit 21 acquires each data corresponding to the print item definition data from the physical distribution information data 260. Further, the control unit 21 acquires the print title name of the portal information data 240 specified from the site ID.

  For example, when the entry content, site ID, site sub ID, and reception email address for two-dimensional code output are set in the print item definition data, the control unit 21 enters the entry content, site sub ID, and reception email address. Are acquired from the physical distribution information data 260. When the two-dimensional code output is set, the control unit 21 converts the set data (for example, a reception mail address) into a two-dimensional code. Next, the control unit 21 generates output data including the converted two-dimensional code, site ID, site sub ID, item name, corresponding data, and print title name, and transmits the output data to the primary customer terminal 51. . The primary customer terminal 51 transmits the received output data to the printer 52 to execute printing. As a result, the distribution slip on which the print title name, entry contents, and the like are printed is output from the printer 52. The primary customer provides the output physical distribution slip to the secondary customer. Thus, the use application process is completed.

(Secondary customer email address acquisition process)
Next, processing when registering a secondary customer's email address will be described.
In this e-mail address acquisition process, the secondary customer causes the secondary customer mobile terminal 56 to read the two-dimensional code of the provided logistics slip. Specifically, the secondary customer mobile terminal 56 reads the two-dimensional code displayed on the physical distribution slip by using the two-dimensional code reading function, converts the two-dimensional code, and acquires the reception mail address.

  In this case, the secondary customer portable terminal 56 activates the mailer and transmits a blank mail to the acquired reception mail address. This empty mail includes the mail address data of the secondary customer who is the sender of the mail.

  The empty mail transmitted from the secondary customer portable terminal 56 is provided to the ASP service engine 20 of the ASP system 10 via the network. The control unit 21 of the ASP service engine 20 extracts, from the logistics information database 26, logistics information data 260 in which the received mail address that is the destination of the empty mail is recorded. Then, the secondary customer email address acquired as the transmission source is recorded in the secondary customer email address area of the extracted distribution information data 260.

(Status browsing process)
Next, the situation browsing process when the secondary customer confirms the situation of the distribution that is the object of transaction will be described with reference to FIG.

  In this case, the secondary customer causes the secondary customer terminal 55 to access the web server 15 using the URL of the primary customer described in the provided logistics slip. The web server 15 transmits the portal site data associated with the designated URL to the secondary customer terminal 55. The portal site data includes a login request button.

Here, when the secondary customer selects the login request button of the portal site, the secondary customer terminal 55 makes a login request to the web server 15.
The web server 15 supplies a login request to the ASP service engine 20. This login request includes the URL data for which the request has been received. Thereby, the control part 21 of the ASP service engine 20 receives the login request with respect to the primary customer specified from URL (step S3-1). Then, the control unit 21 extracts the portal information data 240 having the received URL from the portal information database 24. Then, it is determined whether the login definition data of the portal information data 240 is “password present” or “password not present” (step S3-2).

  Here, in the case of “no password” (“NO” in step S3-2), the control unit 21 executes an output process of a passwordless login screen (step S3-3). Specifically, the control unit 21 acquires the item name (for example, the reception number) corresponding to the use data (site sub ID) of the login definition data from the item name data of the portal information data 240. And the control part 21 produces | generates the login screen data containing the input column of this item name, and transmits to the secondary customer terminal 55 via the web server 15. FIG. The secondary customer terminal 55 displays a login screen based on the received data.

  This login screen includes an item name of the site sub ID, an input field corresponding to the item name, and a send button. On this login screen, the secondary customer inputs the data described in the physical distribution slip into the site sub ID input field. Then, by instructing transmission, the secondary customer terminal 55 transmits the input data to the web server 15. The web server 15 supplies the acquired data to the ASP service engine 20.

  On the other hand, in the case of “having a password” (in the case of “YES” in step S3-2), the control unit 21 executes output processing of a login screen with a password (step S3-4). Specifically, the control unit 21 acquires the item name corresponding to the usage data (site sub ID) of the login definition data from the item name data of the portal information data 240. Then, the control unit 21 generates login screen data including the item name input field and the password input field, and transmits the login screen data to the secondary customer terminal 55 via the web server 15. The secondary customer terminal 55 displays a login screen based on the received data.

This login screen includes a site sub-ID item name, an input field corresponding to this, a password input field, a password setting button, and a send button.
Here, if the password is not yet set, the secondary customer selects the password setting button. As a result, the secondary customer terminal 55 transmits a request for a password setting screen to the web server 15. The web server 15 generates password setting screen data and transmits it to the secondary customer terminal 55. The secondary customer terminal 55 displays a password setting screen based on the received data. The password setting screen includes a site sub ID input field, a password input field, and a setting button. The secondary customer enters the site sub ID and password in the site sub ID input field and password input field. Then, by instructing transmission, the secondary customer terminal 55 transmits the input data to the web server 15. The web server 15 supplies the received data to the ASP service engine 20.

  On the other hand, if a password has already been set, on this login screen, the secondary customer enters the data entered in the logistics slip into the site sub ID entry field, and the set password in the password entry field. input. Then, by instructing transmission, the secondary customer terminal 55 transmits the input data to the web server 15. The web server 15 supplies the acquired data to the ASP service engine 20.

  And the control part 21 of the ASP service engine 20 performs a user authentication process (step S3-5). Specifically, the control unit 21 extracts logistics information data 260 having data that matches the received data from the logistics information database 26. Here, in the case of “no password”, the user authentication is completed when the distribution information data 260 can be extracted.

  On the other hand, if the password is present, the control unit 21 extracts the distribution information data 260 that matches the received site sub ID and password. If the distribution information data 260 can be extracted, the user authentication is completed. When the user authentication is completed, the control unit 21 transmits / receives data to / from the secondary customer terminal 55 directly via the network without passing through the web server 15.

  Next, the control part 21 performs the output process of the screen for secondary customers (step S3-6). Specifically, the control unit 21 acquires the primary customer name and each item name from the portal information database 24. Furthermore, the control part 21 acquires the data output to this secondary customer from the physical distribution information database 26 linked | related with the site sub ID used for user authentication based on the acquired data item. And the control part 21 produces | generates information provision screen data using the acquired data, and transmits to the secondary customer terminal 55. FIG.

The secondary customer terminal 55 displays the information provision screen on the display based on the received information provision screen data. FIG. 10 shows an information provision screen 610 in the book reservation inquiry system, FIG. 11 shows an information provision screen 620 in the vacant seat reservation system, and FIG. 12 shows an information provision screen 630 in the delivery inquiry system. In the information providing screens 610, 620, and 630 shown in FIGS. 10 to 12, corresponding data is displayed at locations corresponding to the data layout diagram 600 shown in FIG.
By browsing such information provision screens 610, 620, and 630, the secondary customer can confirm the status of physical distribution requested to the primary customer.

(Logistics status acquisition process)
Next, the distribution status acquisition process by the distribution status change function will be described. In this case, as described above in step S2-4, in the distribution information data 260 associated with the primary customer using the distribution status change function, an e-mail address for each distribution state is recorded corresponding to each status. In addition, the mail address for each distribution state for two-dimensional code output is also recorded in the print item definition data of the primary customer. For this reason, the distribution state e-mail address displayed by the two-dimensional code is printed corresponding to each status on the distribution slip output when the application for service is made to the primary customer. It should be noted that the two-dimensional code mail address and each status of the two-dimensional code in the distribution slip are separated from other contents and pasted to the distribution.

  After that, when each status corresponding to the distribution state-specific mail address is reached, the primary customer transmits an empty mail to the distribution state-specific mail address corresponding to the status. For example, in the case of a transportation service, it is attached to the requested item and delivered. When the article reaches a predetermined place (for example, a collection / delivery place), an empty mail address is transmitted to the mail address classified by physical distribution state recorded in the physical distribution slip at that place.

  Thereby, the ASP service engine 20 of the ASP system 10 acquires the mail address of the empty mail. Then, the control unit 21 of the ASP service engine 20 extracts the distribution information data 260 in which the acquired mail address is recorded from the distribution information database 26. And the control part 21 acquires the status in which the acquired mail address is recorded in the extracted physical distribution information data 260, and records it in the present status data area of this physical distribution information data 260. Thus, the distribution status acquisition process is completed.

(Notification processing)
Next, the notification process will be described with reference to FIG.
Here, the primary customer transmits his / her URL data, causes the primary customer terminal 51 to access the ASP system 10, and obtains a status list screen of the secondary customer who is his / her customer. This status list screen includes physical distribution information data 260 which is a secondary customer associated with the URL data and whose status is not “completed”, and an update button. The primary customer uses the secondary customer status list screen to update the logistics status related to the logistics whose current status has changed. When the update is instructed, the primary customer terminal transmits the site sub ID for specifying the updated distribution information data 260 and the updated content to the ASP service engine 20. The control unit 21 of the ASP service engine 20 specifies the distribution information data 260 based on the received data, and updates the acquired data.

  When the current status of the secondary customer's logistics is changed by such current status update processing or the above-described logistics status acquisition processing, notification processing is started. In this case, the control unit 21 determines whether or not a situation notification function is provided as a function of the primary customer (step S4-1). Specifically, the control unit 21 specifies the situation notification function in the data area of the standard function or the extended function of the portal information data 240 associated with the site ID included in the physical distribution information data 260 whose current situation has been changed. Determine whether data is recorded.

  If there is a status notification function ("YES" in step S4-1), the control unit 21 performs notification processing (step S4-2). Specifically, the control unit 21 notifies the secondary customer mail address of the distribution information data 260 whose current status has been changed that the current status has been changed.

  On the other hand, when there is no situation notification function (in the case of “NO” in step S4-1), the control unit 21 determines whether or not the updated current situation is arrival, guidance, or delivery (step). S4-3). In this case, when it is neither arrival, guidance nor delivery, the control unit ends the notification process.

Here, when the updated current situation is any of arrival, guidance, or delivery, the control unit 21 executes a completion notification process (step S4-4). Specifically, the control unit 21 notifies the updated current status to the secondary customer mail address of the distribution information data 260 whose current status has been changed. And the control part 21 updates the present condition data of this physical distribution information data 260 to "completion", and complete | finishes a notification process.

  Next, the processing procedure of the primary customer providing the service and the secondary customer for the primary customer using each of the sub-versions of the service inquiry system, the vacancy reservation system and the logistics tracking system will be described.

("Book reservation inquiry system" using sub-version of "Service inquiry system")
First, a “book reservation inquiry system” using a sub-version of the “service inquiry system” will be described. This “book reservation inquiry system” is a system used when the primary customer is “bookstore”, for example.

  In this case, in the sub-version of “service inquiry system”, it is defined that login with “password”, logistic name is input, and one kind of quantity is used. In the print item definition data area of the “service inquiry system”, “entry contents”, “site ID”, “site sub ID”, and “two-dimensional code output mail address” are recorded. For this reason, the same definition data is recorded in the portal information data 240 of the “book reservation inquiry system”. In addition, the primary customer portal information data 240 includes a selection pattern indicating the distribution status of “reception”, “reserving”, “out of stock”, “arrival”, “delivery”, “complete”, “cancellation”. Is selected. In addition, “reservation number” is recorded as the item name of “site sub ID”, and “reservation slip record” is recorded as the print title name. Furthermore, it is set to use a delivery date setting data area as an extended function.

  First, a secondary customer requests a book reservation from the “bookstore” of the primary customer. The primary customer inputs the secondary customer entry contents (name, phone number, book title, quantity, delivery date) using the primary customer terminal 51 and transmits them to the ASP service engine 20. The control unit 21 registers the application for the secondary customer (step S2-1), sets the site sub ID and the reception mail address (step S2-2), and registers the distribution information data 260. In this case, since the distribution status change function is not set in the “book reservation inquiry system” (“NO” in step S2-3), the control unit 21 executes the distribution slip output process (step S2-5). ). In this physical distribution slip, entry contents, a site ID, a site sub ID, and a two-dimensional code reception mail address are recorded, and the title name is “reservation slip record”. This “reservation slip receipt” is delivered from the primary customer to the secondary customer. Thereafter, the primary customer performs an ordering process for the book that has been reserved.

  On the other hand, the secondary customer obtains the two-dimensional code printed on the reservation slip receipt using the secondary customer portable terminal 56, and transmits a blank mail to the reception mail address included in the two-dimensional code. Thereby, the control part 21 acquires the mail address of the portable terminal 56 for secondary customers, and records it on the distribution information data 260 linked | related with the reception mail address.

  Thereafter, when the secondary customer confirms the status of the book that has been reserved, the secondary customer accesses the URL of the site ID recorded in the reservation slip and makes a login request. Thereby, the control part 21 accepts a login request (step S3-1). Here, since the login definition of the primary customer is “with password” (“YES” in step S3-2), the control unit 21 outputs a login screen with a password to the secondary customer terminal 55 (step S3- 4). When the “reservation number” as the site sub-ID and the set password are transmitted to the ASP service engine 20 from the secondary customer terminal 55 in the login screen, the control unit 21 performs user authentication (step) S3-5). When the user authentication is completed, the control unit 21 generates information provision screen data using the physical distribution information data 260 specified by the user authentication, and transmits the information provision screen data to the secondary customer terminal 55 (step S3-6).

  Thereafter, each time the current status of the book reserved by the secondary customer is changed, the current status such as inventory status, arrival, etc., the primary customer inputs and updates the current status of the distribution information data 260. If the updated current status is “arrival” (step S4-3), the control unit 21 executes a completion notification process (step S4-4). Thereafter, when the book reserved by the secondary customer is received, the primary customer sets the current status of the distribution information data 260 of the secondary customer to “complete”. Thus, the service provided by the primary customer to the secondary customer is completed.

("Restaurant vacancy reservation system" using a sub-version of the "vacancy reservation system")
Next, the “restaurant vacancy reservation system” using a sub-version of the “vacancy reservation system” will be described. This “restaurant vacancy reservation system” is a system used when, for example, the primary customer is “restaurant”. Note that a description of the same parts as those of the “book reservation inquiry system” described above will be omitted.

  In this case, the sub-version of the “vacant seat reservation system” is defined as a login with “no password”, a distribution name selected, and two types of quantities used. In the print item definition data area of the “vacant seat reservation system”, data similar to that of the “service inquiry system” is recorded. For this reason, the same definition data is recorded in the portal information data 240 of the “restaurant vacancy reservation system”. The portal information data 240 of the primary customer includes a second distribution name composed of five distribution names of “counter”, “two seats”, “four seats”, “six seats”, and “tatami”. A pattern is selected, and selection patterns indicating six logistics states of “meeting”, “sixth”, “third”, “guidance”, “completed”, and “cancel” are selected. Also, “reference number” is recorded as the item name of “site sub ID”, and “numbered ticket” is recorded as the print title name.

  First, a secondary customer visits a “restaurant” of the primary customer and reserves a seat. The primary customer inputs the entry contents (name, telephone number, desired seat, number of people) of the secondary customer using the primary customer terminal 51 and transmits them to the ASP service engine 20. Using the received entry contents, the control unit 21 registers the application for the secondary customer (step S2-1), sets the site sub ID and the reception mail address (step S2-2), and stores the distribution information data 260. sign up. In this case, the control unit 21 assigns a sequence number (not shown) to the registered physical distribution information data 260. This sequence number corresponds to the “waiting order” when the physical distribution information data 260 is registered. Since the “vacancy reservation system” does not have a distribution status change function (“NO” in step S2-3), the control unit 21 executes a distribution slip output process (step S2-5). In this physical distribution slip, entry contents, a site ID, a site sub ID, and a reception mail address of a two-dimensional code are recorded, and the title name is “numbered ticket”. Then, this “numbered ticket” is delivered from the primary customer to the secondary customer.

  Then, the secondary customer obtains the two-dimensional code printed on the numbered ticket using the secondary customer portable terminal 56, and transmits a blank mail to the reception mail address included in the two-dimensional code. Thereby, the control part 21 acquires the mail address of the portable terminal 56 for secondary customers, and records it on the distribution information data 260 linked | related with the reception mail address.

Thereafter, the primary customer guides the seats as soon as the seats are ready. Then, the primary customer changes the status of the physical distribution information data 260 corresponding to the customer guided to the seat to “completed”. When the status is completed, the control unit 21 specifies the waiting order using the sequence number for the logistics information data 260 waiting for the order. Then, the status of the secondary customer whose waiting order is “1” is changed to “guidance”. Further, the control unit 21 updates the current status of the “third” and “sixth” distribution information data 260 waiting for the turn specified by the sequence number. Here, since the “restaurant vacancy reservation system” has a “status notification function” as a standard function of the “vacancy reservation system” (“YES” in step S4-1), the status of the current status is changed. Moreover, the control part 21 performs a notification process (step S4-2). Thus, the service provided by the primary customer to the secondary customer is completed.

("Delivery status inquiry system" using a sub-version of "Logistics tracking system")
First, a “delivery status inquiry system” using a sub-version of the “distribution tracking system” will be described. This “delivery status inquiry system” is a system used when, for example, the primary customer is a “carrier”.

  In this case, the sub-version of “Delivery Status Inquiry System” defines that login with “no password”, logistics name is input, and one kind of quantity is used. In the print item definition data area of the “service inquiry system”, “entry contents”, “site ID”, “site sub ID”, “two-dimensional code output mail address”, “two-dimensional code output logistics status” “Another mail address” and “status” are recorded. For this reason, the same definition data is recorded in the portal information data 240 of the “delivery status inquiry system”. In addition, in the portal information data 240 of the primary customer, selection patterns indicating the distribution states of “reception”, “delivery”, “arrival at base”, “delivery”, “complete”, “cancel” are selected. ing. Further, “slip number” is recorded as the item name of “site sub ID”, and “invoice record” is recorded as the print title name. Furthermore, in this embodiment, a rich text format field capable of freely recording data is set as an extended function. In this field, the name, address and telephone number of the delivery address are recorded.

  First, a secondary customer requests delivery of an item from a “carrier” of the primary customer. In this case, the secondary customer provides the primary customer with his / her name and telephone number as the sender, the name, address and telephone number of the delivery address, and the article name. The primary customer uses the primary customer terminal 51 to input the secondary customer entry details (your name and phone number, the name, address and phone number of the delivery address, the article name, etc.), and the ASP service engine. 20 to send. The control unit 21 registers the application for the secondary customer (step S2-1), sets the site sub ID and the reception mail address (step S2-2), and registers the distribution information data 260. In this case, since the “delivery status inquiry system” has a distribution status change function as a standard function (“YES” in step S2-3), the control unit 21 sets an e-mail address for each distribution state (step S2). -4). Specifically, the control unit 21 acquires the status used by the primary customer from the distribution status name of the portal information data 240. As a result, the control unit 21 assigns different e-mail addresses to the statuses “accepted”, “delivering”, “arrival at base”, “delivering”, “completed”, and “cancelled”. Then, each status and the corresponding mail address for each distribution state are recorded as distribution information data 260.

  And the control part 21 performs the output process of a physical distribution slip (step S2-5). In this logistics slip, entry contents, site ID, site sub-ID, 2D code acceptance email address, each status and the corresponding 2D code email address for each logistics status are recorded, and the title name is “Invoice Record” It has become. Each status and the mail address according to the distribution state of the two-dimensional code are separated from the “invoice receipt” and attached to the article requested by the secondary customer. The remaining “invoice receipt” is passed from the primary customer to the secondary customer. Thereafter, the primary customer delivers the received article to the delivery destination.

In this delivery, when the article arrives at the base, the primary customer obtains a two-dimensional code corresponding to the status of “delivery” using a two-dimensional code reading terminal, and is included in the two-dimensional code. Send a blank e-mail to your e-mail address. Thereby, the control part 21 of the ASP service engine 20 extracts the distribution information data 260 including the mail address of the transmitted empty mail via the network. Then, the control unit 21 records the status corresponding to the mail address in the current status data area of the extracted physical distribution information data 260. As described above, when the distribution state changes in the primary customer, the control unit 21 updates the current state data of the distribution information data 260 by transmitting a blank mail to the corresponding distribution state-specific mail address. The situation browsing process is the same as the “restaurant vacancy reservation system” described above, and the notification process is the same as the “book reservation inquiry system” described above. When the article is delivered to the delivery destination, the secondary customer's mail address is notified (step S4-4), and the current status is set to “completed”. Thus, the service provided by the primary customer to the secondary customer is completed.

According to this embodiment, the following effects can be obtained.
In the present embodiment, the control unit 21 of the ASP service engine 20 executes a reception mail address setting process in the secondary customer use application process (step S2-2). Thereafter, when a blank mail is transmitted from the secondary customer portable terminal 56 to the set reception mail address, the control unit 21 of the ASP service engine 20 records the reception mail address that is the destination of the blank mail. The distribution information data 260 is extracted, and the mail address data of the secondary customer who is the sender of this empty mail is recorded. For this reason, the control part 21 can acquire a 2nd customer's e-mail address efficiently via the reception e-mail address linked | related with transaction information, and can correlate and record to the corresponding physical distribution information data 260 more reliably. it can. Therefore, it is possible to efficiently acquire the email address of the secondary customer who is the customer of the primary customer and efficiently manage the email address of the secondary customer in association with the physical distribution information data 260 associated with the first customer. it can. Further, the second customer can register a mail address with a simple operation of sending an e-mail.

  In the present embodiment, in the reception mail address setting process, the control unit 21 adds a checksum for the site ID and the site sub ID to the site ID and the site sub ID, and adds a character string and a number sequence obtained by encrypting them. The reception mail address which has is generated. For this reason, even if the reception email address is associated with the site ID and the site sub ID, the site ID and the site sub ID can be prevented from being estimated from the reception email address. Therefore, it is possible to further reduce the possibility that the transaction is tampered with by unauthorized mail transmission from other than the secondary customer.

  In the present embodiment, the secondary customer mobile terminal 56 uses the two-dimensional code reading function to acquire the reception mail address by reading the two-dimensional code displayed on the physical distribution slip. Since the reception e-mail address is not manually entered, the e-mail address of the secondary customer can be more reliably recorded in the corresponding distribution information data 260.

  -In this embodiment, the control part 21 of the ASP service engine 20 is the case where the data which specifies a distribution status change function is recorded on the portal information data 240 of a primary customer in the use application process of a secondary customer (step) In the case of “YES” in S2-3), the distribution state-specific mail address setting process is executed (step S2-4). Thereafter, when each status corresponding to the mail address for each distribution state is reached, the ASP service engine 20 receives an empty mail for the mail address for each distribution state corresponding to the status. The control unit 21 of the ASP service engine 20 extracts the distribution information data 260 in which the acquired mail address is recorded from the distribution information database 26. And the control part 21 acquires the status in which the acquired mail address is recorded in the extracted physical distribution information data 260, and records it in the present status data area of this physical distribution information data 260. For this reason, the current state of distribution can be efficiently updated based on the mail address for each distribution state of the received mail.

In the present embodiment, when the user authentication is completed (step S3-5), the control unit 21 of the ASP service engine 20 acquires the primary customer name and each item name from the portal information database 24, and sends this secondary customer to the secondary customer. Data to be output is acquired from the physical distribution information database 26 associated with the site sub ID used for user authentication. And the control part 21 produces | generates information provision screen data using the acquired data, and transmits to the secondary customer terminal 55. FIG. For this reason, the control part 21 can provide the information regarding the physical distribution containing a present condition to a corresponding secondary customer.

  In this embodiment, when receiving a login request from the secondary customer terminal 55, the control unit 21 of the ASP service engine 20 extracts the portal information data 240 of the primary customer specified from the URL included in the login request. To do. When the login definition data of the portal information data 240 is “password present” (in the case of “YES” in step S3-2), the control unit 21 executes an output process of the login screen with password (step S3). -4). For this reason, depending on the setting of the primary customer, it is possible to avoid information relating to physical distribution from leaking to a third party who does not know the password.

  In the present embodiment, when the current status of physical distribution is updated and there is a status notification function as a primary customer function (in the case of “YES” in step S4-1), the control unit 21 performs notification processing. Perform (step S4-2). If the updated current status is any of arrival, guidance, or delivery, the control unit 21 executes a completion notification process (step S4-4). For this reason, it is possible to notify the secondary customer of the updated current situation or completion.

  In the present embodiment, when a subversion is selected in the portal setting process, the primary customer terminal 51 transmits the subversion identifier data to the ASP system 10. The control unit 21 extracts the login definition, quantity definition, print item definition, and standard function definition data of the template data 220 corresponding to the received subversion identifier, and creates the login definition data area and quantity definition of the created portal information data 240. Recording is performed in each of the data area, the print item data area, and the standard function data area. Next, a selection data setting process in the acquired template is executed (step S1-3). Furthermore, when adding an extended function individually, an extended function is set (step S1-4), and each item name and print title name setting process corresponding to the primary customer is executed (step S1-5). . For this reason, it is possible to set extended functions and item names specific to the primary customer while using templates suitable for each definition and standard function corresponding to the business form of the primary customer, so a portal suitable for the primary customer The site can be generated efficiently.

  In this embodiment, the secondary customer causes the secondary customer terminal 55 to access the web server 15 using the URL of the primary customer described in the provided logistics slip. The web server 15 transmits the portal site data associated with the designated URL to the secondary customer terminal 55. When the web server 15 receives a login request from the secondary customer terminal 55, the web server 15 supplies the login request to the ASP service engine 20. Then, the control unit 21 of the ASP service engine 20 executes user authentication processing (step S3-5), and when this user authentication is completed, the secondary customer terminal is directly connected via the network without using the web server 15. Data is exchanged with 55. Thus, the ASP system 10 can efficiently provide information related to the secondary customer to the secondary customer.

Moreover, you may change the said embodiment as follows.
In the above embodiment, the distribution information data 260 recorded in the distribution information database 26 is provided with data areas for recording the secondary customer mail address and the reception mail address, respectively. Alternatively, the data area for recording the reception mail address and the data area for recording the secondary customer mail address may be shared. In this case, when a service application is received from a secondary customer, the received mail address is recorded in this mail address data area. Thereafter, when the secondary customer email address is acquired using this reception email address, the control unit 21 records the secondary customer email address instead of the reception email address. As a result, it is possible to reduce the memory load and to use an e-mail address that achieves the purpose of acquiring a secondary customer e-mail address.

  In the above embodiment, the e-mail address acquired using the empty e-mail is the e-mail address of the secondary customer mobile terminal 56. If it is a secondary customer's mail address, you may acquire not only a portable terminal but the mail address of the secondary customer terminal 55 carrying a browser program.

  In the above embodiment, the site sub ID is used as login data when performing user authentication in the situation browsing process. The data used for the login data is not limited to the site sub ID, and any data that can identify the distribution information data 260 may be used. For example, a secondary customer's telephone number or email address may be used. In this case, when a plurality of physical distribution information data 260 exist between the same primary customer and the same secondary customer, the corresponding physical distribution information data 260 may be displayed as a list. Specifically, the control unit 21 extracts the relevant logistics information data 260 from the logistics information database 26, and includes a list including information (for example, a site sub ID and a logistics name) for specifying these and the current situation. Generate display screen data. Then, the control unit 21 transmits the generated list display screen data and displays the list display screen on the secondary customer terminal 55. Thereby, the secondary customer can grasp the present situation of physical distribution requested to the primary customer at a time.

  In the above embodiment, in the secondary customer use application process, the control unit 21 acquires the input entry information and information about the secondary customer from the primary customer terminal 51. These pieces of information may be acquired from the secondary customer terminal 55 or the secondary customer portable terminal 56 instead of the primary customer terminal 51.

  In the above embodiment, the description has been made based on the three sub-versions of the service inquiry system, the vacancy reservation system, and the logistics tracking system. However, the present invention is not limited to this, and other subversions may be defined and recorded in the template database 22 as long as they are general-purpose subversions. The sub-version of the “service inquiry system” is used not only for the “book reservation inquiry system” described above but also for a system that manages the status of other orders. The sub-version of the “vacant seat reservation system” is used not only for the “restaurant vacant seat reservation system” described above, but also for other systems, for example, a system for reserving a seat for a vehicle. Further, the sub-version of the “logistics tracking system” delivers not only the above-mentioned “delivery status inquiry system” but also the logistics checked by the secondary customer such as a system for referring to the repair status to the secondary customer request destination. Also used in systems.

1 is a schematic diagram of a system in an embodiment. Explanatory drawing of the data recorded on the template database. Explanatory drawing of the data recorded on the portal information database. Explanatory drawing of the data recorded on the physical distribution information database. The flowchart for demonstrating the process sequence of a portal setting process. The flowchart for demonstrating the process sequence of a secondary customer's use application process. The flowchart for demonstrating the process sequence of a situation browsing process. The flowchart for demonstrating the process sequence of a notification process. Explanatory drawing about the data arrangement | positioning in an information provision screen. Explanatory drawing of the information provision screen in a book reservation inquiry system. Explanatory drawing of the information provision screen in a restaurant vacant seat reservation system. Explanatory drawing of the information provision screen in a delivery status inquiry system.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... ASP system as a service management system, 21 ... Control part, 22 ... Template database as template storage means, 24 ... Portal information database as exclusive site data storage means, 26 ... Transaction data storage means, 1st mail address data Logistics information database as storage means, status data storage means and second mail address data storage means, 51 ... primary customer terminal as first customer terminal, 55 ... secondary customer terminal as second customer terminal, 56 ... first A mobile terminal for a secondary customer as a two-customer terminal.

Claims (5)

A first customer ID for identifying a first customer, a second customer ID for identifying a second customer that is the customer of the first customer, and a transaction between the first customer and the second customer Transaction data storage means for storing transaction information including information related to the progress of the transaction,
First email address data storage means for recording a reception email address associated with the transaction ID;
Portal information storage means in which each status of the logistics state name of the transaction used by the first customer is recorded in association with the first customer ID;
Second mail address data storage means for recording the transaction ID and the mail address according to the state for each status;
A control unit connected via a network to a first customer terminal used by the first customer and a second customer terminal used by the second customer, providing the transaction information to the second customer; A service management system for managing the first customer-only screen used by
The control unit is
Via the first customer terminal screen of the first customer terminal, information related to the transaction with the second customer is acquired, a transaction ID is given, and the transaction ID, the first customer ID, and the transaction with the second customer. Transaction ID giving means for recording information on the transaction data storage means,
Said grant acceptance mail address for transaction ID, a reception mail address providing means for recording the first email address data storing means,
A reception mail address output means for outputting the transaction information and the reception mail address via the first customer dedicated screen;
Each status used for the transaction by the first customer ID is specified in the portal information storage means, a status-specific mail address is assigned to each status, and the second mail address data storage is associated with the transaction ID of the transaction. Means for assigning email addresses according to status to be recorded in the means;
The state-specific e-mail address output means for outputting the state-specific e-mail address associated with the transaction information via the first customer dedicated screen;
When an e-mail is received from the second customer terminal for the reception e-mail address, the e-mail address of the transmission source that has transmitted the e-mail is used as the e-mail address of the second customer associated with the transaction ID. Second customer email address registration means for recording in the transaction data storage means;
When receiving the e-mail for pre SL state by email address, to identify the status and the transaction ID associated with this state per email address, the progress of the transaction specified by the transaction ID, the Progress update means to update the status of the transaction identified from the email address by state ,
Means for transmitting to the second customer's e-mail address recorded in the transaction data storage means a notification that the situation has been changed to the second customer when the progress status relating to the transaction of the second customer is changed; And <br/> a service management system. In addition to the first customer ID, it further comprises dedicated site data storage means for storing screen data dedicated to the first customer of the first customer,
The control unit is
An access request receiving means for receiving an access request including a first customer ID and a transaction ID from the second customer terminal;
First customer dedicated screen data corresponding to the first customer ID included in the access request is acquired from the dedicated site data storage means, and the transaction information corresponding to the transaction ID included in the access request is stored in the transaction data storage. Data acquisition means for acquiring from the means;
Information providing means for generating the information providing screen data for the second customer by incorporating the acquired transaction information into the first customer dedicated screen data and transmitting the data to the second customer terminal; The service management system according to claim 1 , wherein In order to create the first customer dedicated screen data of the first customer, further comprising a template storage means for storing a template for each subversion,
In the template, the distribution pattern selection pattern used in the portal site generated using this sub-version template is recorded,
The control unit is
From the first customer terminal, obtaining data for specifying a subversion used by the first customer, a template selection means for obtaining a template corresponding to the subversion from the template storage means,
Dedicated screen generation means for generating the first customer-specific screen data based on the acquired template and storing it in the dedicated site data storage means;
When data for specifying a distribution state name pattern is received from the first customer terminal, each distribution state name corresponding to the selected distribution state name pattern is acquired from the specified template data. The service management system according to claim 2, further comprising means for recording in the portal information storage means in association with the first customer ID of the first customer . A first customer ID for identifying a first customer, a second customer ID for identifying a second customer that is the customer of the first customer, and a transaction between the first customer and the second customer Transaction data storage means for storing transaction information including information related to the progress of the transaction,
First email address data storage means for recording a reception email address associated with the transaction ID;
Portal information storage means in which each status of the logistics state name of the transaction used by the first customer is recorded in association with the first customer ID;
Second mail address data storage means for recording the transaction ID and the mail address according to the state for each status;
A control unit connected via a network to a first customer terminal used by the first customer and a second customer terminal used by the second customer, providing the transaction information to the second customer; Is a service management method for managing the first customer dedicated screen used by
The control unit is
Via the first customer terminal screen of the first customer terminal, information related to the transaction with the second customer is acquired, a transaction ID is given, and the transaction ID, the first customer ID, and the transaction with the second customer. A transaction ID granting step for recording information on the transaction data storage means;
Said grant acceptance mail address for transaction ID, a reception mail address allocation step of recording the first email address data storing means,
A reception e-mail address output stage for outputting the transaction information and the reception e-mail address via the first customer dedicated screen;
Each status used for the transaction by the first customer ID is specified in the portal information storage means, a status-specific mail address is assigned to each status, and the second mail address data storage is associated with the transaction ID of the transaction. A state-specific e-mail address assignment stage recorded in the means;
A state-specific e-mail address output step for outputting the state-specific e-mail address associated with the transaction information via the first customer-specific screen;
When an e-mail is received from the second customer terminal for the reception e-mail address, the e-mail address of the transmission source that has transmitted the e-mail is used as the e-mail address of the second customer associated with the transaction ID. A second customer email address registration step for recording in the transaction data storage means;
When receiving the e-mail for pre SL state by email address, to identify the status and the transaction ID associated with this state per email address, the progress of the transaction specified by the transaction ID, the A progress update stage that updates the status of the transaction identified from the email address by state ,
When the progress status relating to the transaction of the second customer has been changed, a notification that the status has been changed is sent to the second customer's email address recorded in the transaction data storage means. And a service management method. A first customer ID for identifying a first customer, a second customer ID for identifying a second customer that is the customer of the first customer, and a transaction between the first customer and the second customer Transaction data storage means for storing transaction information including information related to the progress of the transaction,
First email address data storage means for recording a reception email address associated with the transaction ID;
Portal information storage means in which each status of the logistics state name of the transaction used by the first customer is recorded in association with the first customer ID;
Second mail address data storage means for recording the transaction ID and the mail address according to the state for each status;
A control unit connected via a network to a first customer terminal used by the first customer and a second customer terminal used by the second customer, providing the transaction information to the second customer; A service management program for managing the first customer-only screen used by
The control unit
Via the first customer terminal screen of the first customer terminal, information related to the transaction with the second customer is acquired, a transaction ID is given, and the transaction ID, the first customer ID, and the transaction with the second customer. About
Transaction ID giving means for recording information in the transaction data storage means,
Said grant acceptance mail address for transaction ID, reception mail address assignment means for recording the first email address data storing means,
Each status used for the transaction by the first customer ID is specified in the portal information storage means, a status-specific mail address is assigned to each status, and the second mail address data storage is associated with the transaction ID of the transaction. Means for assigning an email address by state to be recorded in the means,
State-specific e-mail address output means for outputting the state-specific e-mail address associated with the transaction information via the first customer dedicated screen;
When an e-mail is received from the second customer terminal for the reception e-mail address, the e-mail address of the transmission source that has transmitted the e-mail is used as the e-mail address of the second customer associated with the transaction ID. Second customer email address registration means for recording in the transaction data storage means;
When receiving the e-mail for pre SL state by email address, to identify the status and the transaction ID associated with this state per email address, the progress of the transactions identified in the transaction ID, the Progress update means for updating the status of the transaction specified from the email address by state , and
Means for transmitting to the second customer's e-mail address recorded in the transaction data storage means a notification that the situation has been changed to the second customer when the progress status relating to the transaction of the second customer is changed; <br/> A service management program characterized by functioning as.

Images