TWM583084U - Multi-person collaborative management system for activity and ticket - Google Patents

Abstract

The present invention is a patent and a ticket multi-person collaborative management system patent, which includes a database unit, an activity creation editing unit, a ticket creation editing unit, a collaborative operation unit, a sales unit, and a ticket. Volume management unit. After any user in the database unit has established an edit ticketing activity, it is not necessary to complete the activity planning and ticket management by itself, but the collaboration unit can be used to link the database unit to the activity. Add one or several designated co-planners to manage activities and tickets together. The ticket management unit can query the database unit through the collaborative operation unit whether the user is designated as a common administrator of the ticket volume. If the query result is yes, the ticket management unit of the user can perform reading and uploading. Go to the database unit to verify that the customer's ticket data is correct. When the activity established by the user and the ticket are issued, other users on the system can purchase the ticket through the sales unit to become a customer.

Description

Activity and ticket multi-person collaborative management system

The present invention relates to a collaborative management system that is built in an event venue where ticket admission is required, in particular, techniques for multi-person simultaneous activity planning, control ticket sales, and multi-person collaborative management ticket verification.

For events such as jogging, market, parties, concerts, exhibitions, etc., the organizers are mostly equipped with a ticketing system to control the sale of event registration and ticket sales. The existing ticketing and event registration system has been able to support physical ticket and electronic ticket simultaneously.

Regardless of whether the event organizer controls the admission or sales registration of the event site through physical ticket or electronic ticket, the site management personnel of the event party must check the ticket purchase of the applicant or the ticket purchaser through paper or electronic files. Information, in a paper-based manner, usually takes a lot of time to compare. It is an efficient way for event organizers to check the identity of a ticket with an electronic file such as an electronic ticket system.

The problem is that checking the personal identity of the ticket purchase through the e-ticket system is only one part of the event. Other activities such as event planning and on-site management require the organizer to bet on a large amount of resources to coordinate management, so that all the staff of the organizer can press Plan to execute the activity process, when the organizer's staff are not familiar with the details of these activities, it will consume more management resources.

In addition, in addition to controlling the customers participating in the event, the event organizer must coordinate external suppliers and event sponsors, which will not only increase the cost of event management, but also require more time for planning and on-site planning. Post-care after the end of management and activities, especially when the scale of the event is larger, often requires more resources to manage collaboratively.

Therefore, it can be understood that the time cost saved by the above-mentioned e-ticket entrance is only a small proportion among the total cost of the overall event, how to combine the electronic ticket data and the existing event holding details, so that the event organizer Every staff member in charge of each department can clearly understand the total cost of the event.

The present invention provides a multi-person collaborative management system for activities and ticket volumes, the management concept of "multi-person division of labor coordination" and the marketing management concept of "sales and management integration", and the coordination activities of the event organizers in the past activities. In order to manage the issue of an activity.

More specifically, the novel system includes a database unit, an activity creation editing unit, a ticket volume creation editing unit, a collaborative operation unit, a sales unit, and a ticket management unit. The database unit can store the details of the activity, the details of the ticket, the management identity data of the user, the management record of the user, the personal identification data of the customer and the purchase record of the customer; the activity establishes an editing unit and connects the database a unit, and configured to receive one of the multi-user provided activity establishment edit confirmation, and establish an edit confirmation according to the activity to establish a corresponding activity creation edit record in the database unit; the ticket volume creation editing unit, the connection activity establishment edit a unit, and configured to receive a multi-user providing one of the ticket volume to establish an edit confirmation, and establish an edit confirmation according to the ticket volume to establish a corresponding ticket volume to establish an edit record to be synchronously recorded in the database unit after the activity creation editing unit The collaborative work unit is connected to the database unit, the activity establishment editing unit, the ticket volume creation editing unit, and the ticket management unit, and is configured to receive a user-defined activity common administrator setting and ticket Volume co-administrator settings, and confirm the establishment of the corresponding activity manager based on this setting The ticket manager is recorded in the database unit. When a user activates the ticket collection module of the ticket management unit, the collaborative operation unit will connect to the database unit and verify whether the user has an administrator status; The sales unit is connected to the database unit and configured to receive a ticket purchase confirmation provided by a customer, and establish a corresponding ticket purchase record based on the ticket purchase confirmation and encrypt the ticket purchase data into the data. a ticket unit; the ticket management unit, the ticket management unit may provide the user to read the purchase password obtained by the customer to be accessed by the ticket management unit via the database unit. Among them, the user After the ticket management unit of the terminal connects the database unit through the collaborative operation unit, the query confirms that the user is designated as the ticket management manager, and if yes, the ticket management unit of the user performs the update. The customer's purchase record in the library unit is 'invoiced'. The ticket management unit of the client may link the purchase record of the customer obtained by the database unit, and if the purchase record of the customer is confirmed after the inquiry, the ticket management unit displays the encrypted information of the purchase ticket obtained after the inquiry. The ticket management unit is read by the ticket management administrator, and the read data is transmitted to the database unit for verification.

Preferably, the new system further comprises a multi-person activity co-editing function, through which the editing unit is established and connected to the collaborative working unit, and the multi-person multiplex activity detail editing function can be synchronously coordinated, wherein the activity details include but are not limited to Maps, routes, itineraries, texts, audio and video materials, etc.

Preferably, the collaborative work unit is further configured to assign a ticket created by the ticket creation editing unit to a user or a multi-user to manage the ticket, and enable the user to receive the receipt through the ticket management unit. The ticket module is used to synchronize the management of the ticket volume.

Other novel features and more detailed technical and functional descriptions of the present invention are disclosed in the following description.

(1) ‧‧‧Database unit

(2) ‧‧‧ Activity creation editing unit

(3) ‧‧‧ ticket creation editing unit

(4) ‧‧‧Collaborative work units

(5) ‧‧‧ ticket management unit

(6)‧‧‧Sales unit

Figure 1 Activity and ticket multi-person collaborative management system

Figure 2 Activity creation editing and ticket creation editing flow chart

Figure 3 Ticket Management Process

The block diagram of the first figure shows a preferred example of the activity and ticket multiplayer collaborative management system of the present invention. It is pointed out that the system includes a database unit 1, an activity creation editing unit 2 is connected to the database unit 1, and a ticket creation editing unit 3 is connected to the activity establishment editing unit. 2, the collaborative work unit 4, a collaborative work unit 4 is connected to the database unit 1 and the activity establishment editing unit 2 and the ticket volume editing unit 3 and the ticket management unit 5, a ticket management unit 5 The database unit 1 is connected to the cooperation unit 4 and the sales unit 6 to connect the database unit 1 and the ticket management unit 5.

Any customer who purchases an event admission qualification to a venue through the system must first establish a personal identity profile in the database unit 1. As is generally known, the personally identifiable information includes, but is not limited to, a data field such as a name, an ID number, an address, a telephone number, and the like. In particular, in addition to being identified as a customer identity, users who wish to use the system to establish activities, establish tickets, manage activities, and manage ticket volumes can also use this identity data to establish and manage activities and ticket volumes. However, the process of establishing a person's identity data is not the place where the new type appeals. In any event, the user or customer uses the system through the personally identifiable information stored in the database unit 1 and is associated with the established activity and ticket or the purchased ticket.

The second figure shows an activity creation editing and ticket creation editing flow chart for explaining the activity and ticket creation and editing process of any user in the database unit 1. For a user who has previously established his personal identification data in the database unit 1, the system first searches for the activity data in the database unit 1 in the database unit 1 according to the identity data of the user. Then, in step b, the active content editing module 200 is activated in the activity creation editing unit 2 and saved in the database unit 1. The active content editing record includes, but is not limited to, an event name and an event time, an activity process, and an event location. , event photo...etc. Then, in step c, the user can activate the activity manager setting module 40 through the cooperation unit 4 and link the database unit 1 to the related management personnel of the activity through step a2. At this time, as in step d, the user The ticket volume creation editing unit 3 can be started synchronously and the ticket management administrator setting module 400 can be set to set the ticket volume administrator of the ticket volume, and then the step e is executed to start the ticket volume creation module 30 under the activity. New ticket volume. In particular, multiple tickets can be created under one activity, and multiple administrators can be set for one ticket. Then, in step f, the user can edit the content of the individual ticket volume by using the ticket volume editing module 300 and save the content in the database unit 1 by the step a3. Edited records include, but are not limited to, the name of the ticket and the activity of the ticket, the amount of the ticket, the currency of the ticket, the refund condition of the ticket, and so on.

For a user who has never established any activity in the database unit 1 before, the event can be stored in the database unit 1 by step a2 after the activity creation module 20 is created in the activity creation editing unit. Then, according to the flow shown in the second figure, the editing settings of the activity and the ticket volume are completed.

For a user who is set as the active co-planner, the record of the co-planner can be searched for the database unit 1 via step a2, and the co-planner verification module 4000 is used to verify whether it is the co-planner of the activity. If the verification result is “Yes”, the active content editing module 200 can be started to synchronize the editing activities via step g. If the verification result is "No", the next action cannot be performed.

From the flow shown in the second figure and related descriptions, it can be understood that the data of each activity and the ticket volume in the database unit 1 is unique, so that it can be understood that the activity ticket created by the user is required. Established under the event, the active user can choose not to create any ticket in the activity. Each activity can be set up by several administrators, and each ticket can also be assigned to several administrators.

The third figure shows a flow chart of the management of the ticket volume, which is used to explain that the ticket of the client is used by any client in the database unit 1 after purchasing the ticket of the activity using the ticket management unit 5b. How the management unit 5a verifies the activity. First, the customer purchases the ticket volume of the activity established by other users of the system through the sales unit 6 in the ticket purchasing module 50b, as in step b2, and, as in step b1, the purchased ticket data will be Stored in the database unit 1. In step a3, for a customer who has purchased a ticket to enter the event at the event site, the customer searches for the ticket data purchased and saved in the database unit 1, and the ticket data is used to pass the ticket display module 500b. Display the purchased ticket data, the displayed data is the encrypted characters, and displayed on the screen by means including but not limited to QR-CODE or BAR-CDOE, but the details of the data encryption and decryption and display are not the novel claims Where it is, let alone the use of the organizer The client is used as the basis for purchasing tickets. Then, in step e, the user of the user terminal uses the ticket volume reading module 500a of the ticket volume management unit 5 to read the encrypted ticket volume data to the database unit through, but not limited to, a lens or infrared rays. 1 Query whether the customer of the client has this purchase record. More specifically, in step c, the client first searches for the administrative authority in the personal identity data in the database unit 1 through the ticket manager verification module 40000 in the collaborative operation unit 4. This event as well as the ticket volume. If the result of the inquiry is "No", the subsequent action of the ticket receiving end module 50a of the ticket management unit 5 cannot be performed. If the query result is "Yes", it means that the user has been designated as the ticket volume administrator, and is the administrator represented by one of the personal identity materials of the database unit 1. At this time, the user terminal continues to query the customer ticket. Whether there is such a purchase record in the purchase record corresponding to the personal identification data in the database unit 1. If the result of the query is "No", the ticket data is not displayed. If the query result is "Yes", it indicates that the customer does have the purchase record in the database unit 1, that is, the ticket receiving module 50a can Perform the invoicing action. At this time, as step a1, the ticket volume management unit 5a of the client uploads the ticket volume data read by the ticket reading module 500a to the database unit 1 to update the ticket collection record to avoid the The purchase record is reused to allow others to enter the event, and the client enters the event at the event site to complete the admission ticket process.

Since the ticket management unit 5 synchronizes the reading of the ticket volume by the multi-person through the collaborative operation unit 4, the multi-person division of labor can quickly identify the identity of each customer, which enables the customer to pass the ticket inspection. Time can be greatly reduced. Compared with the past, the organizer can arrange multiple groups of ticket collectors according to the ticket type, and even authorize the supplier to directly distribute the active goods according to the ticket contents, and then control the quantity and objects of the goods to be distributed by collecting the tickets. The new system Obviously very efficient.

As is generally known, the above-mentioned system of the present invention can be used for jogging, market, party, concert, exhibition, etc., but is not limited thereto. Different from the traditional management system, after the user establishes the editing unit 2 through the activity establishment editing unit 2, one or several activities common planners can be set through the collaborative operation unit 4, and the editor is used to establish the editing. When the unit establishes the ticket volume, it can assign a number of common planners through the collaborative work unit. The ticket management administrator, therefore, the activity and the ticket multi-person collaborative management system simultaneously synchronize the task of the distribution team while planning the activity content, and also perform the establishment and distribution of the ticket volume by the sales unit. Let all members of the management team fully grasp the sales progress of the tickets managed by them, and completely integrate management and sales.

Compared with the traditional activity or electronic ticket entry method, the "multi-person collaborative management" approach of the new system can make the user spend a small amount of time just before the official start of the event. Understand the status of the scene, and transform it into: from the beginning of the activity planning, through the activities of the common planner and the ticket administrator system to fully grasp all the details of their own duties. More importantly, due to the integration of management and sales, users can instantly understand the sales status of the ticket volumes currently managed, so that users can respond to the actual situation on the day of the event as soon as possible, thus making the event execution smoother and safer.

In any case, anyone can get enough instruction from the description of the above examples and understand that the new model is indeed industrially usable. Moreover, the present invention has not seen the same or similar technology disclosed in the same field and is novel and progressive. Therefore, the new model meets the requirements of the new patent and is filed according to law.

Claims (3)

A multi-person collaborative management system for activities and tickets, comprising: a database unit, which can store details of activities, details of ticket volumes, management identity data of users, management records of users, personal identification data of customers and customers a purchase record; an activity creation editing unit, connected to the database unit, and configured to receive one of the multi-user provided activity creation edit confirmation, and establish an edit confirmation according to the activity to establish a corresponding activity to establish an edit record in the database a unit; a ticket roll creation editing unit, a connection activity creation editing unit, and configured to receive a multi-user provided one of the ticket volume creation edit confirmations, and establish an edit confirmation according to the ticket volume to establish a corresponding ticket volume creation edit record After the activity is established, the editing unit is synchronously recorded in the database unit; a collaborative work unit is connected to the database unit, the activity establishment editing unit, the ticket volume creation editing unit, and the ticket management unit, and is configured to be configured Can receive a user-set activity common administrator setting and ticket volume common administrator settings, According to the setting confirmation, the corresponding activity administrator and the ticket manager are recorded in the database unit. When a user starts the ticket collection module of the ticket management unit, the collaborative operation unit will connect to the database. And verifying whether the user has an administrator identity; a sales unit, connecting the database unit, and configured to receive a ticket purchase confirmation provided by a customer, and establishing a corresponding confirmation according to the ticket purchase confirmation The ticket purchase record is encrypted and encrypted into a ticket information unit; a ticket volume management unit, the ticket volume management unit can provide the user to read a customer who wants to enter the store through the ticket management unit to link the database unit Obtaining a purchase password, wherein the ticket management unit of the client connects to the database unit through the collaborative operation unit, and then queries to confirm that the user is designated as a common management administrator of the ticket, if yes, the user The ticket management unit performs an update of the purchase record of the customer in the stock unit as 'invoiced', and the ticket management unit of the client can connect Querying the purchase record of the customer obtained by the database unit, if the customer's purchase record is confirmed after the inquiry, the ticket management management unit displays the purchased ticket encryption data after the inquiry in the ticket management unit for the ticket volume. The administrator reads it, and the read data is transmitted to the database unit for verification. For example, the activity and the ticket multi-person collaborative management system described in claim 1 of the patent application scope, wherein the activity creation editing unit and the ticket creation editing unit are configured by the activity administrator in the collaborative operation unit The activity joint planner verification module and the ticket manager setting module reach a ticket for a plurality of people jointly planning the event and managing the activity. For example, the activity and ticket multi-person collaborative management system described in claim 1 of the patent application scope, wherein the ticket collection module of the ticket management unit is authenticated by the ticket volume verification module in the collaborative operation unit Further configured to perform the collection management of the ticket volume by a plurality of people.