JP2012118663A - Ceremonial occasion supporting system and ceremonial occasion supporting method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system in which information provision is performed, which is necessary for each one of an organizer, representative, and attendant regardless of types and scales of various ceremonial events.SOLUTION: A management server receives event information associated with a ceremonial occasion and an attendant list that is a notification destination of the event information from a representative terminal, and creates a user distribution page on the basis of the event information to distribute the page to addresses in the attendant list. A user who has input attendant information in the user distribution page is specified as an attendant, and the attendant information is recorded in a DB. Information to accept remittance such as a gift of money is also added to the attendant information. A disclosure level attribute is added to the attendant information for respective items, and information to be used for notification is restricted on the basis of the disclosure level attribute depending on a role of the user who is a notification destination of the attendant information.

Description

  The present invention relates to a system and a support method for supporting an organizer who performs various events such as a ceremonial occasion, a representative who notifies the event, and a participant of the event.

  Conventionally, many systems or methods for supporting a ceremonial occasion using a network are known. Many of them are aimed at reducing the burden of fulfilling gold items related to ceremonial occasions, and supporting users who cannot participate directly in ceremonies and event contacts. For example, in Patent Document 1, event information is input from the client's terminal of the ceremonial occasion, a document for the ceremonial occasion is created based on the input event information, distributed to the user, and the document is displayed. A method is described in which the amount of celebration, incense, etc., and personal information of the user are input from the terminal of the user and the return of the reward is arranged from the client terminal.

  In Patent Document 2, a password is distributed to participants in advance, and by entering the password, Internet broadcasts such as ceremonies can be viewed, and the viewing screen shifts to a screen capable of electronic commerce, A system is described that allows viewers to pay money for ceremonial occasions. Patent Document 3 describes a ceremonial occasion information distribution system capable of distributing information related to an event to a contact registered in the security zone when a ceremonial occasion occurs.

  In the method of Patent Document 1, the requester (organizer) of the ceremonial occasion needs to input the e-mail address of the candidate for all information and notification of the event on the system menu page. It is actually difficult for the organizer to enter all of this information. In particular, if the event is a funeral, it is urgent, so the organizer's family, etc. should shorten the candidates for participation in the organization or network (company, school, community, circle, friend, etc.) to which the deceased belonged. It is difficult to examine in time. Therefore, if you cannot enter your contact information, you must rely on word of mouth. In the case of a funeral, the organizer will contact the organization or group of the company, etc. (often a deceased boss or colleague, or the general affairs manager of the organization) But the contacted party does not know all the people involved in the deceased, and will participate even if you are the representative instead of the organizer. I don't want to be concerned with individual information such as the person's address and name, the amount of the incense, the returned goods and the delivery address. On the other hand, the organizer wants to know the necessary information for the participants in order to give a reward, prepare the venue, etc., but it is difficult to obtain the information of all participants in advance. In addition, for users who want to participate in the event after receiving contact (hereinafter referred to as “participants”), regardless of the type and scale of the event, who and how much they have exchanged with gold items such as celebrations and incense in the past. I want to know it all together. This is because the amount of money for the event, such as incense and celebrations, is only considered when the notice is received.

  The method described in Patent Document 2 is a proxy for collecting money associated with a ceremonial occasion for users who cannot participate directly in the ceremony for reasons such as busyness or remoteness. The purpose is for the representative to send information to the contact quickly, but even if each of them supports individual parties individually, the needs of the representative, the organizer and the participants are totaled. Not supported. Ceremonial events include weddings, funerals, legal affairs, childbirth, first verses, Shichigosan, admission / entry, graduation / employment, wedding ceremony, wedding anniversary, changeover / promotion, new construction, moving, retirement, opening / There are various things such as opening of business, longevity celebration, illness / injury visit, disaster visit, etc., and considering that everyone can be the organizer, representative and participant of many events, it depends on the type and scale of the event. It is desirable to have a mechanism that can manage the entire event in a variety of situations.

JP 2001-256319 A JP 2002-83075 A JP 2001-318999 A

  In the present invention, in view of the problems as described above, a ceremonial occasion support system that can provide necessary information to each organizer, representative, and participant regardless of the type and scale of an event such as a ceremonial occasion, and its support It aims to provide a method.

In order to achieve the above object, the ceremonial occasion support system of the present invention has the following functions.
A ceremonial occasion support system in which a plurality of user terminals and a financial institution system including a management server are connected via a network, the management server including event information related to the ceremonial occasion and a notification destination of the event information The user terminal that transmits the participant list is identified as the representative terminal of the event, a user distribution page is generated based on the event information, and the user distribution page is generated to be distributed to the destination of the participant list And a participant who has entered participation information on the user distribution page as a participant, accepts a remittance request information from the participant for a celebration or non-congratulations, and adds to the participation information and records the participant A management unit, adding a disclosure level attribute to each item of the event information and the participation information, and based on the disclosure level attribute, the event information In response to the notification destination role of the user terminal is preliminary the participation information, ceremonial support system and limits the information to be notified.

  According to the above invention, the management server as the core of this system creates an event delivery page based on the event information from the representative terminal and delivers it to the destination described in the participant list. Users who are notified of delivery can apply for participation by entering participation information on the event delivery page, but even if they cannot go directly to the venue, they can send money for celebration / non-congratulation money. Can be added to. At that time, the participation information includes personal information such as address and name, as well as information such as the amount of money to be remittance and account information of the remittance source that the other participants and representatives do not want to know. Disclosure level is added to and the disclosure destination can be limited for each item. By doing so, the user can input the participation information with peace of mind, and unnecessary information is not disclosed to the representative or the organizer.

The system can further include the following functions.
The management server refers to the participant DB, extracts information indicating that the participant wishes to deliver a gold item, creates delivery request data based on the information, and sends the delivery request data to the delivery company system. A home delivery requesting unit for transmitting data is provided.

  According to the above invention, when a participant wants to deliver a gold item directly to the organizer instead of cash transfer, a delivery to deliver directly to the organizer by specifying the amount or goods and adding it to the participation information Service can be requested from this system. In this way, the participant can complete all operations at once.

The system can further include the following functions.
The home delivery requesting section accepts a request for arrangement of money for return from the organizer terminal that is the organizer of the event, creates home delivery request data, and transmits the home delivery request data to the home delivery system.

  According to the above invention, the organizer can arrange to send a return item to the participant for the event. The organizer is notified of at least the address, name, and remittance of the participant, except when the participant refuses to receive it, so the time and effort for the organizer to arrange a return can be reduced.

  In the above system, the organizer terminal and the representative terminal may be different user terminals. This is especially true when the event is a funeral or large-scale, because it is difficult for the organizer to know all the destinations of the candidate, so the organizer and the representative can be set up separately from the organizer. This is to share the roles of each other. In other words, it is possible to reduce the burden of input to each system, such as event organizer and event information details by the organizer, and event summary information and notification destination by the company representative. In this case, the representative does not need to be close to the organizer, and may be a person who handles only notifications in a clerical manner, such as a company general affairs manager.

The system can further include the following functions.
The management server analyzes event information separately input from a plurality of representative terminals, and determines that they are the same event, merges the event information and manages them as one event.

  According to the above invention, when there are a plurality of representatives in a large company or the like (for example, when a deceased person is present in a plurality of departments), the organizers do not know the relationship between the representatives of each other. Even in such a case, when the system analyzes the contents of the separately input event information and determines that they are the same event, it can be managed as one event thereafter. By doing so, it is possible to prevent duplicate input and a plurality of the same event information from flowing from different routes.

The system can further include the following functions.
Based on a request from the user terminal, the management server causes the user terminal to display a usage history related to the event of the user.

  According to the above invention, the user of this system can cross-sectionally list all the information of ceremonial occasions in which money items have been exchanged in the past. If it is displayed and exchanged with the same partner, it can be used as a reference when deciding the amount of celebration and non-celebration for this event. It is also useful for managing annual expenditures for ceremonial occasions.

Moreover, this invention can also be grasped | ascertained as the following ceremonial occasion support methods as another aspect.
A ceremonial occasion support method in a system in which a plurality of user terminals and a financial institution system including a management server are connected via a network, wherein the management server includes event information related to the ceremonial occasion and the event information Identifying a user terminal that transmits a participant list as a notification destination as a representative terminal of the event, creating a user distribution page based on the event information, and distributing to a destination of the participant list; Identifying the user who entered the participation information on the user distribution page as a participant, and recording the participation information, adding a disclosure level attribute for each item of the event information and the participation information, Based on the disclosure level attribute, the information to be notified is limited according to the role of the user terminal that is the notification destination of the event information and the participation information. Ceremonial support method characterized in that it comprises a floor.

  According to the present invention, it is possible to provide a mechanism that satisfies the information needs required for each organizer, representative, and participant regardless of the type and scale of an event such as a ceremonial occasion.

It is a figure showing the outline of the ceremonial occasion support system 1 whole concerning the embodiment of the present invention. It is a figure which shows the function structure of the core part 10 of the ceremonial occasion support system which concerns on embodiment of this invention. It is a figure which shows the user management table and participant management table which concern on embodiment of this invention. It is a flowchart which shows the process sequence of the user delivery page preparation part 14 which concerns on embodiment of this invention. It is a flowchart which shows the process sequence of the participant management part 15 which concerns on embodiment of this invention. It is a flowchart which shows the process sequence of the delivery request part 16 which concerns on embodiment of this invention. It is a figure which shows the ceremonial occasion service main screen and funeral service request screen which concern on embodiment of this invention. It is a figure which shows the screen notified to a user after selecting the funeral service which concerns on embodiment of this invention, and completing input. It is a figure which shows the various party service request screens concerning embodiment of this invention. It is a figure which shows the celebration delivery service application screen which concerns on embodiment of this invention. It is a figure which shows the celebration receipt screen which concerns on embodiment of this invention. It is a figure which shows the deposit / withdrawal management screen and return registration screen which concern on embodiment of this invention.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described in detail with reference to the accompanying drawings. Note that the same number is assigned to the same element throughout the description of the embodiment.

  FIG. 1 is a diagram showing an outline of an entire ceremonial occasion support system 1 according to an embodiment of the present invention. In this system, the ceremonial occasion support system core part 10 (or simply the system core part) is connected to an accounting host computer 10A such as a bank. Together, they may be referred to as the core part 20 of the ceremonial occasion support system in a broad sense.

  The system core unit 10 is connected to user terminals 30, 31, and 32 via a network 70, and is also connected to a delivery company system 40, a gift seller system 50, and other financial institution system 60. "User terminal" refers to the terminal of the user (user) of the service provided by this system, but all users become representatives, participants, and organizers depending on the event. Therefore, when the user's terminal having each role is distinguished from other terminals, the terminal is represented as a participant terminal 30, a representative terminal 31, and an organizer terminal 32. If there is no need to distinguish between them, they are simply called user terminals. The user terminal may be a variety of mobile information terminals such as a general PC (Personal Computer) or a mobile phone that can be connected to the network, but each user terminal is not necessarily a terminal owned by the user side. Alternatively, it may be a terminal on the service provider side that inputs data based on a user request.

  FIG. 2 is a diagram showing a functional configuration of the core part 10 of the ceremonial occasion support system according to the embodiment of the present invention. The system core unit 10 is a computer that functions as a management server of the present system. The main function unit includes a user delivery page creation unit 14, a participant management unit 15, and a home delivery request unit 16, and a related database ( DB: Data Base) includes a user DB 11, a participant DB 13, and a temporary deposit account DB 12. However, the transfer money temporary storage account DB 12 may exist in the host computer 10A. In the figure, the user DB is divided into a participant-side DB and an organizer-side DB for convenience. However, the user DB may actually be the same DB, and there is no particular distinction between the two in terms of mounting.

  The functional configuration described above is merely an example, and one functional unit may be further divided, or a plurality of functional units may be configured as one functional unit. Typically, each functional unit reads a computer program stored in a memory (RAM: Random Access Memory, ROM: Read Only Memory) or a storage device, and a CPU (Central Processing Unit) built in the device. This is implemented by reading and writing necessary data from the DB stored in the storage device and controlling other related hardware (for example, input / output devices and communication interface devices). Is done. Hereinafter, the operation of each functional unit and related data will be described.

  Each functional unit of the system core unit 10 displays various input screens on the user terminal, but for each event, the user ID is associated with the role when the user inputs each service request screen. Based on the user ID and the event ID, the system can detect the role of the terminal. That is, a user who was a participant in a certain event may become a sponsor in another event. Therefore, each screen provided by this system is divided into organizers, representatives, participants, and other general users for each event, and identifiers are added to the screens.

  The user distribution page creation unit 14 receives the input of the service request information 17 from the representative terminal 31, creates event information, and distributes the distribution destination (electronic) of the users who are candidates for the event included in the service request information 17. Event information is distributed to a mail address or a dedicated URL. The event information may be the text of the e-mail, the web page describing the event information, or both.

  The service request information 17 may be input not from the representative terminal 31 but from the organizer terminal 32. However, depending on the scale of the event, the representative of the organization or group is more likely to receive information about the distribution destination than the organizer. In this system, the first input terminal for event information is used as the representative terminal 31. However, the event information can also be updated from the organizer terminal 32. Thus, by separating the roles of the representative and the organizer, the input burden on each is reduced. Of course, the organizer can also serve as the representative. In this case, if the organizer can understand all the participants (inviters), such as a wedding or a close-to party, the organizer can make all inputs without setting up a representative. Is the representative terminal 31 equal organizer terminal 32.

  When the representative completes the input of the distribution destination (or participant list) and event information, the user distribution page 18 is created. The distributed user refers to this page and applies for the event. The contents (participation information) of the user distribution page 18 for which the user has applied for participation will be described in detail later. However, the disclosure destination of information has an attribute of a disclosure level that limits the disclosure destination for each input item, and the information disclosure destination is for each item. Managed. For example, in the contents of the user distribution page 18, only items necessary for the participants are notified to the organizer terminal 32. This is because the organizer only needs to be able to know information only to give back later. The participation information cannot be referred from the representative terminal 31 or other participant terminals 30 unless otherwise specified. This is because the representative does not need to know the personal information of each participant, and the participants do not need to know the personal information of each other. In addition, the user of this system can refer to the details of his / her withdrawal information or deposit information history regardless of the role. As long as exchanges such as money related to the ceremonial occasion are exchanged via this system, all are automatically recorded in the user DB 11 for each user.

  There may be a plurality of representative terminals 31, and they may exist for each organization or group. The organizer knows only the contact information of the representative, and can make event information available to the representative. In addition, when the representative knows a person who can be another representative, the representative can contact the person who can be another representative directly and have him / her become a representative. In addition, the person who became the representative receives event information from the organizer from the representative terminal 31 and inputs it as event information to the system, and inputs the contact information of the candidate candidates. You don't have to participate in the event, so you don't have to be a participant. In the case of becoming a participant, the representative terminal 31 also serves as the participant terminal 30.

  Participant management unit 15 extracts the user who actually displayed the intention of participation from the users to whom the user distribution page creation unit 14 has distributed the event information as “participants” and manages the participation information. Is registered in the participant DB 13. The user is recognized as a participant by inputting his / her necessary information on the user distribution page 18. Of course, it can be canceled before the event starts.

  The money transfer temporary storage account 12 is an account for temporarily storing money in a bank when a user who has indicated his / her intention to participate sends money such as a celebration or incense. Since a mechanism for temporarily storing remittances from users already exists in the bank system as a separate deposit account, this may be used. The participant management unit 15 takes out the transfer information (remittance information) added to the participation information from the transfer money temporary storage account 12 and notifies the home delivery request unit 16 of the transfer information.

  The home delivery requesting unit 16 is connected to the home delivery company system 40, refers to the participation information stored in the participant DB 13, and when the participant receives payment to the temporary deposit account 12 managed by the system, the organizer It has a function to accept a service for delivering a celebration directly to the customer in cash or goods. At present, cash cannot be delivered under the terms and conditions of a general courier, so in that case, an item equivalent to the amount transferred will be given, but a bank and post office have partnered and requested from the client's designated account. A cash delivery service has already been started that allows you to withdraw money and mail it by registered mail, and it is possible to send cash by cooperating with this system.

  In order to become an organizer, representative, or participant of this service, it is necessary to register with this system and receive a user ID, but to receive a user ID, your name, password, and email address However, it is desirable that personal information, account information, and the like thereafter be requested when necessary. As the number of users increases, the usefulness of the system increases. Therefore, a button that allows easy user registration is arranged on the screen for event notification.

  FIG. 3 is a diagram showing a user management table and a participant management table according to the embodiment of the present invention. The user management table is a table for managing the entire user information stored in the user DB 11 and registered in this system. In the user table, as shown in FIG. 3A, in addition to the user ID, name / address / phone number, e-mail address, password, bank account number for deposit and withdrawal, and credit card if necessary Information etc. are included.

  In the personal information in the table, a “disclosure level” is defined for each item, and the range that can be disclosed to other than the user himself / herself is limited. For example, disclosure level 1 information is disclosed to all users or users within the range permitted by the user, disclosure level 2 information is disclosed to the representative or the organizer, and disclosure level 3 information is disclosed only to the organizer. Level 4 is defined to be disclosed only to the user. In the example of the figure, disclosure level 1 is an email address (including user ID), disclosure level 2 is a name / address / phone number, disclosure level 3 is an account number, and disclosure level 4 is an attribute of an item added to a password. Yes. The disclosure level for each item is set by the system according to the type of event, but can be changed by the user. Of course, the definition of the disclosure level can be customized for each user.

  In the user management table, in addition to the above personal information, as individual usage history, the date of use, type of service used, transaction ID, name and user ID of the counterparty, transaction amount, transaction method, self in this system And all interactions in the event, such as the role of the other party. A trading partner is a partner who has exchanged a gift for celebration or non-celebration. Not only the amount of money but also the name of the gift may be recorded. Handed-on exchanges that cannot be grasped by the system can be added to the usage history by the user himself / herself. The usage history can be viewed at any time by the user himself / herself, but it is particularly desirable to be able to refer to the usage history with a single touch from a screen for transferring money. This is because the past history is often referred to at the time of transfer.

  In FIG. 3B, information (participation information) of the user who applied for participation in the event on the user distribution page 18 is recorded. For example, event ID, type of service used, representative user ID, organizer user ID, and the like. In addition, in the participation information (displayed in the <participant list> format in the figure), detailed information on the exchange of money is recorded for each transaction. A disclosure level is also defined for each item of the participation information. The organizer can refer to most of the items except for a part, but representatives and participants are disclosed so that the name or user ID of the participant or the number of participants is disclosed, but otherwise it is not disclosed. Set levels to prevent unnecessary information exchange.

  FIG. 4 is a flowchart showing a processing procedure of the user delivery page creation unit 14 according to the embodiment of the present invention. First, in step S10, the user delivery page creation unit 14 waits for a service start request from the user terminal. If there is a service start request, the input screen is transmitted according to the type of requested service (step S11). Next, in step S12, it is checked whether or not the input data satisfies the minimum necessary items defined for each event. If not, correction is requested. If all the input data checks are OK, the process proceeds to step S13, and a notification mail to the user (participation candidate) is created based on the input information. It is desirable for the notification mail to have several templates prepared for each event. At this time, the user distribution page creation unit 14 recognizes the terminal (user ID) that transmitted the service start request as the representative terminal 31.

  Next, in step S14, the user distribution page creation unit 14 creates a user distribution page 18 for the user (participation candidate), and in step S15, a link to the service application page is first added to the notification mail. Append. If an additional page is required depending on the service content or event, the link destination is added (step S16). For example, a link to a page describing the venue location, telephone number, and access is added. Finally, a notification mail is transmitted to the destination of the entered participant list (step S17). Note that the notification mail is transmitted by e-mail, and there is a page dedicated to notifications depending on the company. In that case, the notification mail may be linked from the dedicated page, and the URL may be the destination.

  The user who has received the notification mail opens the service application page linked to the notification mail, and when it is determined that the event should be participated, clicks the participation application column or the like. When remitting celebrations, incense, etc., the payment method (bank transfer, credit card payment) or home delivery service (described later) can be specified. Of course, the participant may go to the venue and hand over a congratulatory gift, but in that case, clicking on the hand-off column will help to grasp the number of participants. Information input by the participant is managed as event information for each event and stored in the user DB 11 and the participant DB 13. If the user who has received the notification mail is not a user of this system, it is desirable that the user can be registered immediately from the notification screen. You can click on the application form without registering, but you cannot use automatic remittance or home delivery services.

  FIG. 5 is a flowchart showing a processing procedure of the participant management unit 15 according to the embodiment of the present invention. The participant management unit 15 has a function of managing a user who has applied for participation from the user distribution page 18 as a participant and managing each event.

  First, in step S20, the participant management unit 15 checks whether the current time has reached the service end time, and ends the process if the service end time has been reached. The service end time is a time during which a service can be accepted that is predetermined for each event. For example, it is set to 1 hour before the start of the event or several days after the end of the event. The service end time is defaulted by the system according to the type of event, but can also be set by the organizer or representative.

  If it is during the service time, the participant management unit 15 always refers to the user distribution page in step S21 and waits for a participation application. When there is an application for participation and there is a request for automatic remittance (step S22; Yes), the processing is divided as follows according to the deposit method. In the case of remittance from the bank providing this service, a transfer request screen is transmitted to request payment (step S23). At this time, the transfer destination may be the bank account of the organizer if permitted by the organizer, or may be a separate deposit account prepared exclusively by the bank for this service. The deposit transferred from the participant is temporarily stored in this separate deposit account, and then transferred to the organizer's account. By doing so, the organizer can receive payment without notifying the participant of the account number. Further, when the deposit is made by transfer from another bank, the other bank settlement waiting process is performed (step S24). In the case of credit card settlement, a credit card settlement screen is transmitted and settlement is waited (step S25). Since the details of these deposit processing procedures are widely performed, description thereof will be omitted.

  Participant management section 15 records the transaction data in participant DB 13 after checking that all input data is OK in step S26 and that payment is completed in step S27 (step S28). However, if it takes time to make a payment, such as a transfer from another bank, record the intermediate situation once. Even if the participant does not use automatic remittance, other data is recorded.

  FIG. 6 is a flowchart showing a processing procedure of the home delivery request unit 16 according to the embodiment of the present invention. The home delivery requesting unit 16 has a function of arranging a service for delivering money and goods to the organizer according to the wishes of the participants. The home delivery request section 16 meets the needs of participants who think that it is rude to just transfer money such as celebrations to the organizer's account, and organizers who want to reduce the burden of delivering money to participants when returning such as incense return Therefore, it has a function that works in conjunction with the home delivery system.

  First, in step S30, the home delivery request unit 16 waits until the current time reaches the application page (user delivery page) closing time. The application page closing time may be the same as the service end time in FIG. 5, but is determined in consideration of the convenience of the courier.

  Next, in step S31, the home delivery requesting unit 16 searches the participant DB 13 and checks whether there is incomplete data despite the request for home delivery. For example, there is a case where transfer from another bank is not completed even after a predetermined period. If there is incomplete data, a notification mail to that effect is sent to the incomplete data participant (step S32). At the same time, the person in charge may make a telephone call.

  Thereafter, the home delivery request unit 16 once closes the participant DB 13 (step S33). Then, information necessary for home delivery (sender, destination, remittance amount or product name / product number, delivery date / time, etc.) is extracted from the participant DB 13 and home delivery data (home delivery request data) is created (step S34). These processes are repeated until there is no participant having a home delivery request (step S35).

  The home delivery request unit 16 collects the home delivery data of all the participants, transmits them to the home delivery company system 40 (step S36), and waits until a home delivery acceptance completion notification is received (step S37). When a delivery receipt completion notification is received from the delivery company system 40, a delivery receipt completion notice is transmitted to the participant (step S38). In the above processing procedure, since the period of the ceremonial event is usually short, a closing time is set for each event in order to increase processing efficiency, and the home delivery data is sent to the courier system 40 after the closing time. However, each time a home delivery service request occurs, home delivery data may be created and transmitted.

  FIG. 7 is a diagram showing a ceremonial occasion service main screen and a funeral service request screen according to the embodiment of the present invention. A user (host or representative) who wants to start a service in the system when an event occurs, first selects a service name on the ceremonial occasion service main screen 100 and logs in. Of course, the main menu may be displayed after the login is completed. In the main menu, a menu of services provided by the system is displayed. Menus include, for example, weddings / banquets 101, funerals 102, various celebrations 103, legal matters 104, various parties 105, etc., which can be serviced at any time, such as acquisition management 107, as well as requests for services when an event occurs There is a service that can be accepted even after the event ends, such as the return arrangement 108. Although not specifically shown, since there are various other types of ceremonial occasions, those menus may be prepared individually. The acquisition management 107 and the return arrangement 108 can also be requested from each service. The first user registers as a user in this system by pressing the user registration 109.

  Here, as an example, a funeral service request screen 110 when the user selects the funeral 102 is shown on the right side of FIG. On this screen, various input items for registering funeral event information are displayed. Each input item is added with the disclosure level as described above as an attribute. In the case of funerals, what is entered on this screen is often the representative of the organization or group, not the organizer. This is because it is not easy for the organizer to know the members related to the deceased in the organization. The representative who has received contact from the organizer first selects an attribute such as organization (company, school / alumni association, friend, neighborhood association, etc.) in the input area 111 on this screen. In this example, it is assumed that “company” is selected. The representative then inputs representative information 112 and organizer information 113 such as his / her name, company name, department, address, etc., but a user who has already become a representative at the same funeral. If so, display that information as well. This is because if there is a user who is already a representative, duplicate input such as organizer information can be avoided, and if there is another representative in the same company, the input of the distribution destination can be shared for each group.

  The representative inputs participation candidates who may participate in the funeral as participation candidate information (participant list) in the input area 114 based on the employee list or the departmental list. Here, the minimum required input items may be an e-mail address, name, and department, and it is not necessary to fill in all items. If you have entered candidate candidate information in the past as a representative, it will be displayed on the initial screen, so you only need to make additional corrections. In addition, the destinations of the participation candidates may be input individually, but since there are many cases where the number of participants is large, it is desirable that the participation candidates are received by a CSV (Comma Separated Values) file or a tabular file. In addition, if there is a dedicated page for notifying an in-house intranet or the like, the URL may be used instead of the list of participants.

  Finally, the representative inputs a message to be notified to the participation candidate in the input area 115. There are several types of notification sentence templates provided by the system according to the event, so only the necessary parts need to be corrected. When the representative finishes inputting the above data, he presses the send button to end the event registration. After that, there is no need to do anything as a representative. The system merges any events that match the organizer information (same date, location, and organizer need not be exact), and notifies each representative or organizer of the event. Also good.

  FIG. 8 is a diagram showing a screen that is notified to the user after the funeral service according to the embodiment of the present invention is selected and input is completed. In the previous figure, when the necessary information is entered from the funeral service request screen, as shown in FIG. 8, a notification e-mail 120 and an incense delivery service application screen 130 are created and notified to the participating candidates. .

  Candidates who have received the notification email 120 can confirm the location of the night and funeral, etc., but if they want to transfer the incense but cannot directly attend, click on “Incense delivery service” The incense delivery service application screen 130 is displayed. The participant inputs necessary personal information from this screen and selects a payment method. Further, a message 133 to be sent to the organizer can be entered. Needless to say, an attribute of a disclosure level is added to each input item.

  If the participant has an account with the bank providing this system, the amount of the incense will be transferred from his / her account to the bank's separate deposit account dedicated to this service (later the organizer's account) Can be transferred automatically). Of course, transfer from another bank and payment by credit card are also possible. In addition, participants who attend the funeral directly can transfer only incense with this system. In that case, the reception at the funeral hall says so. For attendees, there is no need to put cash in a bag, and the organizer also has the risk of handling a large amount of cash for the funeral receptionist, which is beneficial for both parties.

  In the screen 130, when the participant determines the amount of the incense to be transferred, the user can easily check his / her own deposit / withdrawal history regarding the past ceremonial occasion by pressing the use history button 131. The usage history screen 140 at the right end of FIG. 8 is an example of this display. The usage history can display all past records exchanged via this system stored in the user DB 11. The display format can be sorted and displayed by any method selected by the user, such as by exchange procedure, by date, by money, by event, by role, etc. Although not specifically shown, it is assumed that data directly exchanged between users without going through this system can be directly input by the user from this screen or another input screen. Identification information indicating that these data are also manually input is added and stored in the user DB 11. Further, a message input field 133 to be sent to the organizer may be added to the screen 130. Furthermore, a sentence example button 134 may be provided to display a message example sentence.

  FIG. 9 is a view showing various party service request screens according to the embodiment of the present invention. In a party event, unlike a funeral, it is usually easy for an organizer to decide participants (inviters). The following example assumes a small party, but for a large party where participants cannot be identified, multiple representatives enter event information on behalf of the organizer, just as in funerals. You can deal with it.

  In the figure, various party service request screens 150 are shown. As described above, in this system, the user ID of the user who inputs event information on the service request screen is recognized as the representative of the event. This example shows a scene where the party is relatively small and the organizer himself is the representative and inputs event information. The items to be entered in the representative information 151 and the participant list 153 are almost the same as in the above funeral example, but the organizer information 152 does not need to be entered if it is the same as the representative. There may be a plurality of representatives. That is, when another user separately inputs event information input by a certain user, both events are merged and the same event ID is added when the identity is detected by the system. Moreover, the user who input later also becomes a representative.

  In addition, when the partner who sends the money using this system is different from the organizer, it is necessary to input the information of the destination separately. This is a case where the representative / organizer holds another human celebration as in the example of the figure. However, at this time, a disclosure level different from that of the normal organizer may be defined for the destination. For example, it is possible to devise such that a notification from the system is not sent to a delivery destination that defines a disclosure level 9, but is sent to the representative instead.

  In addition, the notice sentence shown in the lower part of the figure is the same as the previous figure in that the prepared template is modified, but not only the link 155 to “Celebration delivery service” but also the template, As in this example, the attendance table 150 may be linked. You may display a message input column on the attendance table linked from the notification sentence. The information entered in the attendance table is normally disclosed to the representative (organizer), so that it can be used for attendance management. Assuming that the user who received the attendance table 160 is not a user of this system, a user registration button 169 may be arranged so that user registration can be performed directly from this attendance table.

  FIG. 10 is a diagram showing a celebration delivery service application screen according to the embodiment of the present invention. Basically, it is the same as the screen of the incense delivery service in the center of FIG. 8, but unlike incense, a service for sending gift certificates and goods by home delivery in addition to cash is added. When sending an article, a link button 173 to an online shop specializing in gifts is affixed, so that the screen may be shifted to a normal online shop screen. However, even in that case, it is possible to receive purchase information from the gift seller system 50 and leave the transaction record in the user DB 11.

  Further, as shown in the right usage history screen 180 in FIG. 10, in the usage history of this event, as the deposit / withdrawal method, the item name of the gift and the link to the product information page 182 are displayed instead of cash exchange. It may be. By doing this, gift sellers will also increase the exposure opportunities of the products, so I feel a merit in linking with this system.

  FIG. 11 is a diagram showing a celebration reception screen according to the embodiment of the present invention. As shown in the figure, a celebration delivery message 175 is delivered to the recipient of the celebration by e-mail or the like. From the celebration delivery message 175, the linked celebration receipt confirmation screen 185 can be directly opened, and the contents of the celebration (transfer person, celebration amount, message, etc.) and confirmation that the celebration has been transferred can be confirmed. .

  FIG. 12 is a diagram showing a deposit / withdrawal management screen and a return registration screen according to the embodiment of the present invention. In the deposit / withdrawal management screen 190 of FIG. 12A, all records of events related to the ceremonial occasion recorded in the user DB 11 are displayed. As described above, the usage history screen can also be displayed from the application screen for each service, but it is also possible to input information on deposits directly exchanged between users, although not shown.

  The return registration screen 200 in FIG. 12B is a screen for the organizer to register return for the participants. In return, it is customary to return with gift certificates or goods instead of cash. Depending on the region, it is common to send items corresponding to half (half turn) or one-third of the amount received. On the return registration screen 200, as shown in the figure, information of all participants who have received a celebration or non-congratulation is displayed in a list format for each event. Sorting can be done in order of group or amount of money. In this system, return items for all participants can be registered together from this return registration screen 201.

  When the organizer presses the return gift list button 201, a gift product list (groceries such as gift certificates, tea, glue, coffee, and household goods) is displayed. When “Return” is selected, gift certificates corresponding to half of the amount received in the return item column of each partner are collectively input. It is the same even if one-third return or other product is selected. It is also possible to make a difference in the goods according to the amount of money, not the same goods. For example, “a gift certificate of 10,000 yen or more is a gift certificate”, “5,000 yen or more is a coffee”, and “3,000 yen or less is a tea” can be selected. Of course, by pressing 202 buttons for each participant, the product can be selected individually. The selected product information is sent to the delivery company system 40 by the home delivery requesting unit 16 and the home delivery service is executed.

  9, 10, and 11, the service content of the ceremonial occasion support system 1 has been described by taking funerals and events of various parties as examples. However, even in the case of other events, it is required for each event. Since the input items are slightly different, the system can handle various events.

  As for the type of ceremonial occasion, in addition to marriage, funeral, legal affairs, various parties shown in the main menu of FIG. There are various things such as promotion / promotion, new construction, moving, retirement, opening / opening, longevity celebration, illness / injury visit, disaster visit, etc. You can manage all the deposits and withdrawals related to ceremonial occasions and receive necessary services when an event occurs. In particular, the same user sometimes becomes an event organizer, sometimes a representative, or a participant, but in this system, managed information suitable for each role is provided. This system also requires financial institutions such as banks, which are service providers, to cooperate with other service providers. However, the usefulness of this system increases as the number of users increases for financial institutions. By providing this service, the number of users will increase naturally, leading to the acquisition of depositors.

  As mentioned above, although this invention was demonstrated using embodiment, it cannot be overemphasized that the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiments. Further, it is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

10 Core part of ceremonial occasion support system 10A Account host computer 11, 11A, 11B User DB
12 Transfer account temporary storage account DB
13 Participant DB
14 User distribution page creation unit 15 Participant management unit 16 Home delivery request unit 17 Service request information 18 User distribution page 20 Core part of ceremonial occasion support system 30 User (participant) terminal 31 User (representative) terminal 32 User (organizer) terminal 40 Delivery company system 50 Gift seller system 60 Other financial institution system 70 Network 120 Funeral delivery message 130 Incense service application screen 140 Usage history screen 150 Various party service request screen 160 Attendance table screen 170 Celebration Delivery service application screen 175 Celebration delivery message 180 Usage history screen 185 Celebration receipt confirmation screen 190 Deposit / withdrawal management screen 200 Return registration screen

Claims (7)

A ceremonial occasion support system in which a plurality of user terminals and a financial institution system including a management server are connected via a network,
The management server
Identify the user terminal that sent the event information on the ceremonial occasion and the participant list that is the notification destination of the event information as the representative terminal of the event, create a user distribution page based on the event information, A user delivery page creation unit that delivers to the destination of the participant list;
A participant management unit that identifies a user who has entered participation information on the user distribution page as a participant, receives remittance request information for a congratulatory or non-congratulatory money from the participant, and records it in addition to the participation information; With
A disclosure level attribute is added to each item of the participation information, and information to be notified is limited based on the role of the user terminal that is a notification destination of the participation information based on the disclosure level attribute. Ceremony support system.   The management server refers to the recorded participation information, extracts information indicating that the participant desires delivery of a gold item, creates delivery request data based on the information, and sends the delivery request data to the delivery company system. 2. The ceremonial occasion support system according to claim 1, further comprising a home delivery requesting section for transmitting home delivery request data.   The home delivery requesting unit accepts an arrangement request for money items for return from the organizer terminal that is the organizer of the event, creates home delivery request data, and transmits the home delivery request data to the home delivery system. The ceremonial occasion support system according to Item 2.   The ceremonial occasion support system according to claim 3, wherein the organizer terminal and the representative terminal are terminals of different users.   The management server analyzes event information separately input from a plurality of representative terminals, and determines that the event information is the same event, merges the event information and manages as one event. The ceremonial occasion support system according to 1 to 4.   The ceremonial occasion support system according to claim 1, wherein the management server displays a usage history related to the event of the user on the user terminal based on a request from the user terminal. A method for supporting a ceremonial occasion in a system in which a plurality of user terminals and a financial institution system including a management server are connected via a network,
The management server is
Identify the user terminal that transmits the event information about the ceremonial occasion and the participant list that is the notification destination of the event information as the representative terminal of the event, create a user distribution page based on the event information, Delivering to a participant list destination;
Identifying the user who entered the participation information on the user delivery page as a participant, receiving a remittance request information from the participant for the celebration or non-congratulations, and adding and recording the participation information,
Adding a disclosure level attribute to each item of the participation information, and including limiting the information to be notified based on the role of the user terminal that is the notification destination of the participation information based on the disclosure level attribute. A characteristic ceremonial occasion support method.

Images