JP2023184254A - Event management device, program, and event management method - Google Patents

Abstract

To provide an event management device and others, which reduce the work load associated with events such as wedding ceremonies and wedding receptions.SOLUTION: An event management device is provided, comprising a reception unit for receiving settings of event information on an event from a terminal at an event site, and a creation unit configured to create an online invitation format reflecting the event information by inputting the event information to corresponding parts of an online invitation to the event.SELECTED DRAWING: Figure 2

Description

The present invention relates to an event management device, a program, and an event management method.

When holding an event such as a wedding or reception, various preparations are required in advance. Examples include finding a wedding venue, creating a list of invited guests, and deciding on tables and seating on the day of the reception. The bride and groom, who are the parties involved in the event, must spend a great deal of effort and time in order to prepare, such as having multiple meetings with the person in charge of the ceremony hall.

In view of these circumstances, for example, Patent Document 1 proposes a system that supports communication between the parties, the person in charge of the ceremony hall, and the guests in order to smoothly proceed with preparations leading up to the wedding.

Japanese Patent Application Publication No. 2013-178657

By the way, at events such as weddings and receptions, various tasks are required in addition to the above-mentioned tasks. For example, it is necessary to create and send invitations, and manage attendance of guests, but these tasks are unfamiliar to brides and grooms, and are a heavy burden.

The present invention has been made in view of the circumstances described above, and one of its objects is to provide an event management device etc. that can reduce the workload associated with events such as weddings and receptions. .

An event management device that is one aspect of the present invention includes a reception unit that receives event information settings related to an event from a terminal at an event venue, and a reception unit that receives event information settings from a terminal at an event venue. The main feature is to include a creation section that creates an online invitation format that reflects the

According to the present invention, it is possible to reduce the workload associated with events such as weddings and receptions.

1 is a diagram showing a schematic configuration of an event management system according to the present embodiment. FIG. 2 is a block diagram showing the main functions of an event management server. 3 is a flowchart showing the overall flow of the system. FIG. 3 is a diagram illustrating a venue setting screen. It is a figure which illustrated the party registration screen. FIG. 2 is a diagram illustrating an initial screen of a web invitation. It is a figure which illustrated the edit screen of a web invitation. It is a figure which illustrated the screen transition of the management screen regarding a web invitation. It is a figure which illustrated the screen transition of the management screen regarding a web invitation.

Embodiments of the present invention will be described in detail below with reference to the drawings. In this embodiment, an event management system that manages events such as weddings and receptions will be described as an example.

A. Present Embodiment FIG. 1 is a diagram showing a schematic configuration of an event management system 1 according to the present embodiment.
The event management system 1 is installed in a ceremony hall where an event is held, and includes a ceremony hall terminal 10 used by a person in charge of the ceremony hall (wedding planner, etc.), a party terminal 20 used by parties involved in the event such as a bride and groom, and an event management system 1. It is configured to include a guest terminal 30 used by guests invited to the event (for example, relatives and friends of the bride and groom, bosses and colleagues at work, etc.), and an event management server 40 that manages the event.

The ceremony hall terminal 10, the party terminal 20, the guest terminal 30, and the event management server 40 are connected via a communication network N. Note that the ceremony hall terminal 10, party terminal 20, and guest terminal 30 will be referred to as terminals 10, 20, and 30 unless there is a particular need to distinguish them. Further, the number of terminals 10, 20, and 30 can be arbitrarily set depending on the content of the event.

The communication network N includes a communication network that allows information to be exchanged between each terminal 10, 20, 30 and the event management server 40. The communication network N may be, for example, the Internet, LAN, leased line, telephone line, in-house network, mobile communication network, Bluetooth (registered trademark), WiFi (Wireless Fidelity), other communication lines, or a combination thereof. It does not matter whether it is wired or wireless.

Each terminal 10, 20, 30 is configured with, for example, a personal computer (PC), a notebook PC, a tablet terminal, a handheld computer device, a wearable terminal, a mobile phone, a smartphone, etc. Equipped with a browser etc. Each of the terminals 10, 20, and 30 operates software, a browser, etc. according to instructions from the user, thereby enjoying various services provided by the system 1.

For example, in the case of the ceremony hall terminal 10, data regarding the venue of the event and the parties to the event inputted by the person in charge of the ceremony hall may be sent to the event management server 40, or a page provided by the event management server 40 (for example, a web page ) can be displayed on the display. Note that the software may be installed in each terminal 10, 20, and 30, but a configuration in which some or all functions of the software are provided from the event management server 40 or the like via the communication network N (so-called (SaaS (Software as a Service), etc.).

The event management server (event management device) 40 is a general-purpose computer, and may be composed of one computer or a plurality of computers distributed over a communication network. The event management server 40 includes a control device 41 and a storage device 42. The control device 41 includes, as hardware, a CPU, memory such as ROM or RAM, an input interface, an output interface, a communication interface, a bus connecting these, and the like. The control device 41 provides various support functions for reducing the workload of each person involved in the event by having the CPU execute a program stored in a ROM or the like. Specifically, the control device 41 provides a function that supports the creation of a web invitation when an event is held, and a function that supports the management of responses and congratulations from guests to whom the web invitation has been sent (described later). . Note that a "web invitation" is a web page for event invitation created by a party involved, and means an invitation that can be sent online using a dedicated URL, email, or the like. The storage device 42 is a hard disk drive or the like.

FIG. 2 is a block diagram showing the main functions of the event management server 40.
As shown in FIG. 2, the functional module includes an account management section 411, a reception section 412, a creation section 413, a display control section 414, and a transmission section 415.

The account management unit 411 manages the accounts (for example, unique information including ID and password) of each user who uses the system 1, and accepts logins using each account.

The reception unit 412 receives various information regarding the event (for example, venue information, party information, etc., which will be described later) from each terminal 10, 20, and 30.

The creation unit 413 creates a web invitation in accordance with instructions from the bride and groom who are the parties involved. Here, the "web invitation" is a web page for event invitation created by the person concerned, and is an invitation that can be sent online using a dedicated URL, email, etc.

The display control unit 414 controls the content displayed on each terminal 10, 20, and 30.
The transmitter 415 transmits various information including the web invitation to each terminal 10, 20, 30.

(1) Flow of the entire system The overall flow of the system 1 will be described below with reference to the flowchart shown in FIG. 3 and the like.

<Setting venue information (step S1)>
A person in charge of the ceremony hall attempts to log in to the event management server 40 using the ceremony hall terminal 10. If the login is successful, the person in charge operates the ceremony hall terminal 10 to display the venue setting screen.

FIG. 4 is a diagram illustrating the venue setting screen P1.
The person in charge sets various information (hereinafter referred to as "venue information") IF1 regarding the venue, such as the name, address, and telephone number of the venue, according to the guidance on the venue setting screen P1. The set venue information is transmitted from the ceremony hall terminal 10 to the event management server 40. When the event management server 40 receives venue information from the ceremony hall terminal 10, it stores the received venue information in the storage device 42 in association with a unique ID.

<Registration of party information (Step S2)>
The parties to the event (in this case, the bride and groom) go to the ceremony hall and have a meeting with the person in charge of the ceremony hall regarding the event. The person in charge operates the ceremony hall terminal 10 to display a party registration screen.

FIG. 5 is a diagram illustrating the party registration screen P2.
Following the instructions on the party registration screen P2, the person in charge will enter the event information, including the names of the bride and groom, the type of event to be held (wedding, reception, or both), date, wedding venue name, banquet name, etc. Various information (hereinafter referred to as "party information") IF2 regarding the parties concerned is obtained and registered in the ceremony hall terminal 10. The registered party information is transmitted from the ceremony hall terminal 10 to the event management server 40. When the event management server 40 receives the party information from the ceremony hall terminal 10, the event management server 40 stores the received party information in the storage device 42 in association with a unique ID.

<Creating a web invitation (step S3)>
After completing the registration of party information, the person in charge of the ceremony hall performs procedures for issuing a web invitation account exclusively for the party (hereinafter referred to as "party account"). When this procedure is performed, a guide email for registering a party account is sent to the party terminal 20. The guidance email includes, for example, a URL for account registration and an authentication code. The party uses the party terminal 20 to connect to the URL for account registration, and then enters the authentication code and registers the account. When the authentication is successful and account registration is completed, it becomes possible to log in to the initial screen of the web invitation provided by the event management server 40.

FIG. 6 is a diagram illustrating the initial screen P3 of the web invitation.
As shown in FIG. 6, the previously registered party information IF2 is reflected on the initial screen P3 of the web invitation. Specifically, when the event management server 40 logs in, the event management server 40 reads the corresponding party information IF2 from the storage device 42 and inputs it into the corresponding part of the initial screen of the web invitation, thereby creating a web page as shown in FIG. An initial screen of the invitation (online invitation format) P3 is generated and displayed on the party terminal 20. The parties check the event information in which "names of the bride and groom" and "date of event" are initially reflected as party information IF2. If there is no modification to the party information IF2, the party enters other necessary information (for example, venue name, etc.) and then clicks the registration button to proceed with editing the web invitation. On the other hand, if there is anything to be corrected in the party information IF2, the party operates the party terminal 20 to make the corrections, and then clicks the registration button. In FIG. 6, "names of the bride and groom" and "date of event" are reflected as party information IF2, but other information may be reflected.

FIG. 7 is a diagram illustrating an example of the web invitation editing screen P4.
As shown in FIG. 7, the previously registered venue information IF1 and party information IF2 are reflected on the web invitation editing screen P4. Specifically, upon receiving an instruction to edit a web invitation from a party, the event management server 40 reads the corresponding venue information IF1 and party information IF2 from the storage device 42, and inputs them into the corresponding locations on the web invitation editing screen. By doing so, a web invitation editing screen (online invitation format) P4 as shown in FIG. 7 is created and displayed on the party terminal 20. In Figure 7, "venue name", "address", and "telephone number" are reflected as venue information IF1, and "bride and groom's names", "date", "wedding venue name", and "banquet name" are reflected as party information IF2. " is reflected, but other information may also be reflected.

The parties concerned confirm the venue information and party information that are initially reflected. If there is a modification to this information, the party makes the modification by operating the party terminal 20, while if there is no modification, the party creates a public web invitation. Specifically, by operating the party terminal 20, the party can input the information text for the web invitation, input a message to the guest, input an image to be embedded in the web invitation, select a design, and enter guest response items. Instruct the settings, online gift settings, etc. The event management server 40 creates a web invitation for publication by inputting the information instructed by the parties to the web invitation in which venue information and party information are initially reflected. Thereafter, when the save button is clicked by the party involved, the event management server 40 stores the created web invitation in the storage device 42 along with the ID that identifies the party.

The parties perform procedures to publish the web invitation so that the guests can view the created web invitation. Screens related to the web invitation (initial screen, editing screen, etc.) can be shared between the parties and the person in charge of the ceremony hall.

<Publishing web invitation (step S4)>
Prior to publishing the web invitation, the person concerned sets the presence or absence of a viewing password. If you want to set a viewing password, enter the password of your choice and save it. The party then refers to the disclosure confirmation screen displayed on the party's terminal 20 and performs a final confirmation of the web invitation. If the party determines that there is no problem, the party operates the party terminal 20 to issue an instruction to issue the URL of the web invitation or to send the web invitation. When such an operation is performed, the event management server 40 issues a URL of a web invitation and sends it to the designated guest. Note that the party may send the URL of the issued Web invitation to the guest terminal 30 of each guest using email or SNS (Social Networking Service). Furthermore, in order to facilitate responses to attendance, a QR code (registered trademark) for responses may be printed on the web invitation.

<Confirm attendance at event (step S5)>
When the guest receives the web invitation (including the URL of the web invitation) via email or SNS, the guest operates the guest terminal 30 to display the web invitation. When the guest confirms the web invitation, he or she operates the guest terminal 30 to indicate whether or not to attend the event to which he or she has been invited, and also pre-pays for the gift (including membership fees, etc.) using a credit card or the like.

The event management server 40 receives basic information about the guest (for example, guest ID, name, email address, etc.) from the guest terminal 30 as well as response information indicating attendance at the event and congratulatory gift information indicating the content of the congratulatory gift (amount, etc.). Receive information. The event management server 40 stores the received guest's basic information, reply information, and gift information (hereinafter collectively referred to as "guest information") in the storage device 42, and also transmits the guest information to the ceremony hall terminal 10 and party terminal 20. do. By operating the ceremony hall terminal 10 and the party terminal 20, the person in charge of the ceremony hall and the party concerned can check the response information and gift information of each guest in real time.

<Deposit of gift (Step S6)>
When the deadline for responses from each guest to the web invitation (i.e., each guest's response information and congratulation information) arrives, the person in charge of the ceremony hall operates the ceremony hall terminal 10 to send the congratulation information to the event management server 40. Make a deposit request. When the event management server 40 receives a request to deposit a gift, it determines the amount to be deposited based on the gift information of each guest collected by the deadline, and transfers the amount to a bank account designated by the ceremony hall. Here, the deposited amount can be, for example, the amount obtained by subtracting the system usage fee from the total amount of each gift information (total payment amount). In this case, the system usage fee may be paid separately by the parties to the ceremony hall. On the other hand, the person in charge of the ceremony hall uses the ceremony hall terminal 10 to confirm that the gift has been transferred to the designated account (that is, the gift has been received), and ends the process. Note that the transfer of the congratulatory gift may be confirmed by checking the scheduled payment of the transfer, for example, information on whether the deposit request was successful, the scheduled date of deposit, the amount of the deposit, etc.

According to this system, when creating a web invitation, venue information and party information registered in advance at the ceremony hall are initially reflected (see FIG. 7). As a result, it is possible to eliminate the complicated work of inputting venue information and party information into a web invitation, and it is possible to dramatically reduce the work of the party holding the event.

(2) Flow from the creation of a web invitation to the end of publishing the web invitation Next, refer to Figures 8 and 9 for the flow from creating the web invitation to the end of publishing the web invitation. I will explain.

FIGS. 8 and 9 are diagrams illustrating screen transitions of management screens regarding web invitations. Each management screen is generated by the event management server 40 and displayed on the party terminal 20.

As shown in FIGS. 8 and 9, the display contents of the management screen P5 change depending on the status of the web invitation. Further, the management screen P5 displays operation buttons (manipulators) for enabling operations according to the status of the web invitation.

<Web invitation status: Not created (see A in Figure 8)>
The event management server 40 displays a "Create Invitation" button B1 that prompts the party to create a Web invitation. When the party clicks the "Create Invitation" button B1, the status of the Web invitation changes to "Creating".

<Web invitation status: Under creation (see B in Figure 8)>
The event management server 40 displays a status label Lb1 indicating "unpublished" and a "continue editing" button B1 in an invitation area Ar1 that displays an overview of the Web invitation. Furthermore, the event management server 40 adds an attendance area Ar2 that displays guest attendance status (attendance information) and the like. In this embodiment, it is assumed that the outline of the web invitation includes a preview image of the web invitation, a status label (status information) representing the status of the web invitation, and deadline information representing the response deadline and time. However, the settings of what information is included in the web invitation summary can be changed. Thereafter, when the party concerned completes the creation of the web invitation, the status of the web invitation changes to "completion completed/unpublished".

<Web invitation status: Creation completed/unpublished (see C in Figure 8)>
The event management server 40 displays an "edit" button B3 for editing the web invitation and a "send to guest" button B4 for sending the web invitation to the guest in the invitation area Ar1. When the party concerned clicks the "send to guests" button B3 and the web invitation is sent to each guest, the status of the web invitation changes to "publicly available."

<Web invitation status: Now open (see A in Figure 9)>
The event management server 40 changes the status label Lb1 of the invitation area Ar1 to "open to the public". Furthermore, when confirmation of the attendance status is started by each guest replying their attendance, etc., the event management server 40 activates the "guest list" button B5 and displays information on the gathering status of the celebrants (congratulation information). Add a congratulations area Ar3 that displays things like. In addition, when the event management server 40 receives an attendance response from each guest terminal 30, the event management server 40 updates and displays attendance information indicating the guest's attendance status (here, the number of guests attending and the number of absentees) in the attendance area Ar2 in real time. do.

As shown in A of FIG. 9, the gift area Ar3 includes the number of people who received gifts (number of recipients) N1, the total amount of gifts received (total payment amount) N2, and the usage fee for this system 1 (system Congratulatory information such as N3 (usage fee) and N4 (total payment amount minus system usage fee) that can be deposited is displayed. When each guest makes advance payment for the gift using the guest terminal 30, the event management server 40 updates the gift information displayed in the gift area Ar3 in real time based on the details of the advance payment. Thereafter, when the response deadline (deadline) for the web invitation arrives, the status of the web invitation changes to "after deadline." Note that the deadline for the web invitation may be appropriately set by the party concerned.

<Web invitation status; after deadline (see B in Figure 9)>
The event management server 40 displays a message M1 indicating that the event has been "closed" in the web invitation area Ar1. Further, when the event management server 40 receives a request for payment of a gift from the ceremony hall terminal 10, it displays an icon Ic1 representing the "amount fixed" of the gift in the gift area Ar3. Further thereafter, when the publication deadline of the web invitation arrives, the status of the web invitation shifts to "disclosure completed". As with the deadline, the deadline for publishing the web invitation may be appropriately set by the parties concerned. Further, the deadline and the publication deadline do not necessarily need to be set to different dates and times, and may be set to the same time. Furthermore, the publication may be automatically terminated after a predetermined number of days have elapsed from the event date, for example, one week, or the disclosure may be terminated at any timing by setting the web invitation to private by the person concerned.

<Web invitation status: Publication completed (see C in Figure 9)>
The event management server 40 changes the status label Lb1 of the invitation area Ar1 to "Publication Ended", and also removes the "Edit" button B3 and the "Send to Guest" button B4 that were previously displayed in the invitation area Ar1. You want to hide. Furthermore, the event management server 40 notifies the parties that the publication of the Web invitation has ended by displaying a message M2 to the effect that publication of the Web invitation has ended above the invitation area Ar1. Note that the management screen related to the Web invitation described above can be displayed not only on the party terminal 20 but also on the ceremony hall terminal 10.

According to this system, a summary of the web invitation, attendance information showing the guest's attendance status, and gift information showing the details of the gift are displayed on the same management screen. Those involved in the event can immediately grasp the overview of the web invitation, attendance information for each guest, congratulatory information, etc. by simply checking the management screen, reducing the administrative burden on those involved compared to conventional methods. becomes possible.

B. Others The present invention is not limited to the embodiments described above, and can be implemented in various other forms without departing from the gist of the present invention. Therefore, the above embodiments are merely illustrative in all respects, and should not be construed as limiting. For example, each of the above-mentioned processing steps can be arbitrarily changed in order or executed in parallel as long as there is no inconsistency in the processing contents.

1... Event management system, 10... Ceremony hall terminal, 20... Party terminal, 30... Guest terminal, 40... Event management server, 41... Control device, 42... Storage device, 411... Account management section, 412... Reception section, 413... Creation unit, 414... Display control unit, 415... Transmission unit.

Claims (5)

A reception department that accepts event information settings related to the event from a terminal at the event venue;
An event management device comprising: a creation unit that creates an online invitation format in which the event information is reflected by inputting the event information into a corresponding location of an online invitation for the event. The event information includes venue information regarding the event venue and party information regarding parties to the event,
The event management device according to claim 1, wherein the creation unit creates the online invitation format in which the venue information and the party information are reflected. The event management device according to claim 2, wherein the creation unit creates a public online invitation by inputting other information instructed by the party into the online invitation format. to the computer,
a step of receiving event information settings related to the event from a terminal at the event venue;
creating an online invitation format that reflects the event information by inputting the event information into a corresponding part of the online invitation for the event;
A program to run. A computer-implemented event management method, comprising:
a step of receiving event information settings related to the event from a terminal at the event venue;
creating an online invitation format that reflects the event information by inputting the event information into a corresponding part of the online invitation for the event;
event management methods including;

Images