EP1966747A2 - Systeme et procede pour gerer une commande de ticket - Google Patents

Systeme et procede pour gerer une commande de ticket

Info

Publication number
EP1966747A2
EP1966747A2 EP06844744A EP06844744A EP1966747A2 EP 1966747 A2 EP1966747 A2 EP 1966747A2 EP 06844744 A EP06844744 A EP 06844744A EP 06844744 A EP06844744 A EP 06844744A EP 1966747 A2 EP1966747 A2 EP 1966747A2
Authority
EP
European Patent Office
Prior art keywords
ticket
order
print
module
proof
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP06844744A
Other languages
German (de)
English (en)
Other versions
EP1966747A4 (fr
Inventor
Jeffrey P. Jooste
Sheila A. Babine
Perry Clifton Hart, Jr.
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Avery Dennison Retail Information Services LLC
Original Assignee
Avery Dennison Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Avery Dennison Corp filed Critical Avery Dennison Corp
Priority to EP13178374.8A priority Critical patent/EP2660758A1/fr
Publication of EP1966747A2 publication Critical patent/EP1966747A2/fr
Publication of EP1966747A4 publication Critical patent/EP1966747A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]

Definitions

  • the present invention relates generally to the retail industry and more particularly to ticketing services in the retail industry.
  • FIG. 1 there is shown a simplified block diagram of one common version of the retail supply chain, the retail supply chain being identified generally by reference numeral 11.
  • a retailer 13 places a purchase order (i.e., an order to purchase product at a specified price) with a supplier 15, the purchase order placement step being represented generally by arrow 17.
  • supplier 15 instructs a manufacturing facility 19 (e.g., a factory) to manufacture the particular product for purchase in accordance with the purchase order, the instruction step being identified generally by arrow 21.
  • a manufacturing facility 19 e.g., a factory
  • articles of commerce are traditionally provided with one or more forms of identification media (also referred to herein simply as tags, tickets or labels) to communicate pertinent information relating to the articles.
  • identification media also referred to herein simply as tags, tickets or labels
  • an article of clothing is commonly provided with a permanent label, fabric label or a woven label which may inform a consumer of, among other things, the name of the manufacturer and/or instructions for washing the article.
  • an article of clothing is commonly provided with a removable price tag which is designed for separation from the article after purchase, the removable tag informing a consumer of, among other things, the price, size and style of the article at the point-of-sale.
  • a carton (or other similar type of shipping container) is often provided with an adhesive-backed label to display, inter alia, pertinent shipping information relating to the carton as well as information relating to the contents contained therein.
  • tags tags
  • tickets tickets
  • price tags etc.
  • references to "manufacturing” and “production” of tags, labels or tickets signify the imprinting and/or encoding of these media, not the fabrication of the media.).
  • the production costs associated with the printing, sorting, packing and shipping of individual labels are often too large for a product manufacturing facility to absorb.
  • many retail companies often out-source either a portion or all of their ticketing services to a specialist in the ticketing industry.
  • Avery Denniso ⁇ Corporation of Pasadena, California is widely regarded as an innovator and pioneer in the retail ticketing services industry.
  • TICKET EXPRESSTM which is a well-known retail ticketing service presently commercialized by Avery Dennison Corporation, utilizes a network-based ticketing system to promote efficient and accurate ticket production and management services.
  • the ticketing services may be alternatively directed to a ticketing service bureau 23 that specializes in retail ticketing services (e.g., Avery Dennison Corporation's TICKET EXPRESSTM retail ticketing service bureau). It is to be understood that the ticket request placed with ticketing services bureau 23 is typically placed by either supplier 15 (as represented by arrow 25 in Fig. 1 ), manufacturing facility 19 (as represented by arrow 26-1 in Fig. 1 ) or retailer 13 (as represented by arrow 26-2 in Fig.1).
  • supplier 15 as represented by arrow 25 in Fig. 1
  • manufacturing facility 19 as represented by arrow 26-1 in Fig. 1
  • retailer 13 as represented by arrow 26-2 in Fig.
  • ticketing service bureau 23 instructs an affiliated print center 26 to generate all the necessary tickets for the purchase order, the ticket generation instruction being represented generally by arrow 27.
  • the affiliated print center 26 is located at manufacturing facility 19. However, it is to be understood that print center 26 may alternatively be located anywhere outside of manufacturing facility 19.
  • the manufactured tickets are directed to the packing/shipping warehouse for manufacturing facility 19 where the tickets are then affixed to the products or product cartons for sale. At this time, manufacturing facility 19 carries out its product packing process. The packaged articles are then transferred from manufacturing facility 19 to a freight consolidator 29 for shipment, this transfer step being identified generally by arrow 31.
  • consolidator 29 then ships the packaged articles to a specified retailer distribution center 33 (e.g., a retailer warehouse) in the most efficient and economically advantageous manner, as represented generally by arrow 35 in Fig. 1.
  • the packaged articles are then delivered from distribution center 33 to retailer 13, the delivery step being generally identified by reference numeral 37.
  • the product is then displayed for sale, thereby completing the closed-loop supply chain cycle.
  • TICKET EXPRESSTM is a well-known retail ticketing service bureau which utilizes a network-based ticketing system to promote efficient and accurate ticket production and management services. Although well-known and widely used in commerce, most conventional network-based retail ticketing services suffer from a notable shortcoming.
  • a system for managing the production of tickets in accordance with a ticket order comprising (a) a ticketing services bureau adapted to receive the ticket order and generate an on-screen ticket proof in accordance therewith, (b) a client connected to the ticketing services bureau via an electronic network, wherein said client is capable of retrieving the on-screen ticket proof from the ticketing services bureau and dynamically modifying the on-screen ticket proof so as to yield an edited on-screen ticket proof, and (c) at least one print center assigned by the ticketing services bureau to print tickets in accordance with the ticket order and the edited onscreen ticket proof, the at least one print center being connected to the ticketing services bureau via an electronic network.
  • a method by which a client may review a ticket proof generated by a ticketing services bureau comprising the steps of (a) creating a dynamic, on-screen print proof at the ticketing services bureau, (b) electronically retrieving the dynamic, on-screen print proof from the ticketing services bureau by the client, (c) examining the on-screen ticket proof by the client, and (d) dynamically modifying the on-screen ticket proof by the client so as to yield an edited ticket proof that is retained by the ticketing services bureau.
  • Fig. 1 is a simplified block diagram of a prior art version of the retail supply chain
  • Fig. 2 is a schematic representation of a novel system for production of tickets for use in conjunction with the retail supply chain, the system being constructed according to the teachings of the present invention
  • Fig. 3 is a schematic representation of selected modules of the system shown in Fig. 2, the schematic representation being useful in understanding how a ticket order is captured by the ticketing system of the present invention
  • Fig.4 is a schematic representation of selected modules in the system shown in Fig. 2, the schematic representation being useful in understanding how a ticket proof is generated and interactively reviewed by a client within the ticketing system of the present invention
  • Fig. 5 is a schematic representation of selected modules in the system shown in Fig. 2, the schematic representation being useful in understanding how an approved ticket proof is then used to execute a ticket order by the ticketing system of the present invention
  • Fig. 6 is a schematic representation of selected modules in the system shown in Fig. 2, the schematic representation being useful in understanding how a ticket order is released for printing the ticketing system of the present invention
  • Fig. 7 is a schematic representation of selected modules in the system shown in Fig.2, the schematic representation being useful in understanding how a released job order is printed at the print center;
  • Fig. 8 is a schematic representation of selected modules in the system shown in Fig. 2, the schematic representation being useful in understanding how financial documents are processed by the ticketing system of the present invention;
  • Fig. 9 is a schematic representation of selected modules in the system shown in Fig.2, the schematic representation being useful in understanding how generated tags are affixed to articles of commerce and packaged in accordance with the client- specified instructions;
  • Fig. 10 is a flow chart depicting the process by which the ticketing system shown in Fig. 2 provides ticket management services for the retail supply chain. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • Ticketing system 111 comprises a ticketing services bureau 113 which is electronically linked with at least one print center 115 via the internet 117 (or any other similar communication network).
  • ticketing services bureau 113 is designed to receive a ticket order (i.e., an order for the manufacture of customer-designed tickets) and, in turn, manage the production of said tickets in compliance with the ticket order.
  • ticketing system 111 is described herein in conjunction with the manufacture of tickets that are to be affixed to articles of commerce. However, it should be noted that ticketing system 1 11 is not limited to the management of the production of tickets that are to be affixed to articles of commerce. Rather, it is to be understood that ticketing system 111 could be used in conjunction with the management of the production of any printed item without departing from the spirit of the present invention.
  • tickets in conjunction with system 111 is meant to encompass any well-known form of identification media that is provided with printed matter.
  • system 111 is designed for use with either of the two following paradigms of identification media: (1 ) identification media with relatively standardized formatting attributes (e.g., font type, font size, printed matter layout, etc.), such as conventional price tickets and shipping labels, and (2) identification media with relatively unique formatting attributes, such as fabric labels or other similar types of media which allow for the customer to implement item- specific design characteristics thereto.
  • relatively standardized formatting attributes e.g., font type, font size, printed matter layout, etc.
  • identification media with relatively unique formatting attributes such as fabric labels or other similar types of media which allow for the customer to implement item- specific design characteristics thereto.
  • system 111 enables a customer to interactively modify non-stylistic attributes associated with a ticket, such as size, style, price, description code, country of origin, etc.
  • non-stylistic attributes associated with a ticket such as size, style, price, description code, country of origin, etc.
  • stylistic attributes associated with a ticket such as font type and/or font size, which are typically "givens" for a particular ticket type (e.g., conventional price tickets).
  • system 111 enables a customer to interactively modify most or all attributes associated with a ticket including, inter alia, the stylistic attributes associated with a ticket, such as font characteristics (e.g., font, type, font size, bold/italic/underline, scale, etc.) and layout (e g , rotation, margins, field positioning, etc )
  • font characteristics e.g., font, type, font size, bold/italic/underline, scale, etc.
  • layout e g , rotation, margins, field positioning, etc
  • ticketing system 11 1 is represented herein as comprising a single print center 115 for purposes of simplicity only.
  • ticketing system 111 preferably includes a plurality of print centers 115, wherein each p ⁇ nt center 115 can be provided with a broad range of printing capabilities
  • each print center 115 preferably provides at least some of the following capabilities: digital pnnting capabilities, thermal printing capabilities and offset printing capabilities.
  • ticketing services bureau 113 can select the appropnate print center 115 to execute the print order based on the geographic distribution of print orders (i.e. , by locating the print center 115 closest to manufacturing facility 19), as will be desc ⁇ bed in greater detail below.
  • the selection of a print center 115 to execute the p ⁇ nt order also can take into account the printing capabilities of different print centers.
  • Ticketing services bureau 113 is a global ticket order management system and, as a consequence, is also referred to herein simply as a global order capture application (GOCA)
  • GOCA 113 includes a plurality of modules for carrying out its various functions, each module including a collection of routines that perform a system-level function that may be dynamically loaded and unloaded from a running kernel as required.
  • GOCA 113 is designed to have an open architecture so as to alloyv for the addition, removal and/or replacement of the various individual modules as deemed necessary.
  • GOCA 113 comprises a commerce module 119, a format manager module 121, a digital asset manager module 123, an order management module 125, an optimization manager module 127, a batch manager module 129, a manufacturing module 131 , a warehouse management module 133 and a financials module 135 .
  • the details of each module will be described further in detail below
  • Commerce module 119 is preferably run through an International Business Machines (IBM), Inc., WebSphere TM Commerce server and is responsible for, among otherthings, providing a means for supply chain clients as well as internal users (e.g., customer service personnel for the ticketing services bureau) to interface with GOCA 113. In this capacity, commerce module 119 effectively serves as an e-commerce storefront for ticketing services bureau 113. It should be noted that commerce module 119 is preferably designed to allow for the rapid development and deployment of new software to facilitate in the ordering process as well as to create customer-specific stores that can be maintained by the customer.
  • IBM International Business Machines
  • WebSphere TM Commerce server is responsible for, among otherthings, providing a means for supply chain clients as well as internal users (e.g., customer service personnel for the ticketing services bureau) to interface with GOCA 113.
  • commerce module 119 effectively serves as an e-commerce storefront for ticketing services bureau 113.
  • commerce module 119 is preferably designed to allow for the rapid development and deployment of
  • Format manager module 121 Is preferably run using a custom Java solution that utilizes print-from-the-web (PFTW) technology. Format manager module 121 is responsible for, among otherthings, managing the design, layout and editing of the variable information relating to a ticket order (as well as the relationship of the variable information to pre-printed information). Examples of variable information that is commonly found on a ticket include price information, size information, style information and identification codes relating to the product to which the ticket is to be affixed.
  • PFTW print-from-the-web
  • format manager module 121 is responsible for generating a web-based proof which (1 ) can be interactively reviewed and modified by the client, (2) accurately reflects the particular print characteristics of the target printer for the print job, (3) shows the relationship between the static and variable data, and (4) accurately reproduces images on finished tickets including pre- printed graphics and other stock elements, all of these features serving as principal novel features of the present invention.
  • Digital asset manager 123 is preferably run through a web-based enterprise application suite for digital asset management, such as Interchange Digital's Parts
  • Digital asset manager 123 is responsible for, among other things, the management of tag graphics that are often found on the front of a tag
  • Order management module 125 is preferably run using a scalable back-end e-commerce infrastructure solution that provides comprehensive and flexible realtime order management, such as Yantra Corporation's PureCommerce software. Order management module 125 is responsible for, among other things, the overall management of the ticket order received by commerce module 119.
  • Optimization manager module 127 is preferably a custom Java-based solution that is responsible for, among otherthings, developing the most space-efficient (i.e., optimized) layout of tags on the substrate (e.g., sheet of paper) on which the tickets are to be printed.
  • the substrate e.g., sheet of paper
  • Batch manager 129 is preferably a scheduling software tool that is responsible for, inter alia, optimizing the production of tickets at a selected manufacturing site by consolidating (i.e., batching) similar orders in production runs.
  • Manufacturing module 131 is a preferably a business logic software suite (e.g., Infor's SyteLine ERP solution) that is responsible for, inter alia, the print planning operations for GOCA 113, as will be described in detail below.
  • a business logic software suite e.g., Infor's SyteLine ERP solution
  • Warehouse management module 133 is preferably a software application that is responsible for, inter alia, the management of the delivery of manufactured tags to the warehouse facility 19 where, in turn, said tags are affixed to their associated products and packaged in compliance with specified packing instructions.
  • Financials module 135 is responsible for, inter alia, the management of invoices and related financial documents with respect to the ticket order. It should be noted that module 135 may be represented using a PeopleSoft financials system.
  • Print center 115 represents one available facility where tickets can be produced.
  • Print center 115 includes a print manager module 137 which is preferably a custom solution that is responsible for, inter alia, managing print streams as well as the one or more printers 139 which are responsible for the actual printing of the tickets.
  • print center 115 is represented herein as a single printer 139 for purposes of simplicity only, it is to be understood that each print center 115 Is preferably provided with a variety of different printer types, such as thermal printers, laser printers, offset printers and/or digital printers, each printer having unique printing characteristics. It should be noted that, if print center 115 engages in flexographic and/or offset printing, print center 115 may additionally include a prepress 141 for generating printing press plates.
  • system 111 is designed to undertake each of the tasks identified below:
  • Order Capture i.e.. Commerce Management
  • commerce module 1 19 serves as the user interface (both internally and externally) for ticket order capture and, therefore, serves as the principal "store front" forweb- based order placement.
  • the process by which a ticket order is captured includes the following steps:
  • the supply chain customer places a ticket order with ticketing services bureau 113.
  • the customer may directly place the ticket order with GOCA 113 through commerce module 119 (i.e., through an internet- based store front), whereby customer-specific sales catalogs or websites that are stored within commerce module 119 are utilized to facilitate the order placement process.
  • the customer may place a ticket order electronically via electronic data interchange (EDI).
  • EDI electronic data interchange
  • the customer may place a ticket order to a customer service representative for ticketing services bureau 113 by telephone or facsimile. In turn, the customer service representative manually enters the ticket order into GOCA 113 through commerce module 119.
  • commerce module 119 standardizes the information in the ticket order.
  • the standardized ticket order is then sent from commerce module 119 to order management module 125 which, in turn, assumes the remaining responsibility of managing the ticket order, as will be described in detail below.
  • the non-variable information relating to the ticket order (e.g., customer name, order number, etc.) is sent back to commerce module 119 from order management module 125.
  • the variable field information relating to the ticket order (e.g., price, size and style information relating to an article of commerce) is first identified by format manager module 121. If it is a manual order entry, it is displayed by commerce module 119 for input. Commerce module 119 then captures the variable data entered by the user. Validation is then performed on the variable data information by format manager module 121 and the updated variable information is sent back to commerce module 119.
  • Commerce module 119 provides password-protected security for system 111 , with role-based access for authorized supply chain participants (e.g., retailer 13, supplier 15, etc.).
  • authorized supply chain participants e.g., retailer 13, supplier 15, etc.
  • Ticket Proofing i.e.. Format Management
  • Ticket Proofing relates to the means by which the customer may review an electronic ticket proof file prior to ordering and, if necessary, directly modify any of the variable information associated therewith.
  • the customer is provided with an interactive, dynamic web-based tag proofing system, thereby allowing for customer collaboration on tag design, which is highly desirable.
  • the process by which a ticket proof is created, reviewed and, if necessary, modified by the customer includes the following steps:
  • Format manager module 121 identifies the variable and non-variable information from the ticket order using its ticket repository. The format manager module 121 then extracts the non-variable tag information for the ticket order. Examples of non-variable tag information may include standardized images for a ticket(e.g., stored graphics/artwork) as well as the overall specs of the tag (e.g., size, type, etc.). (2) Format manager module 121 then retrieves the variable information relating to the ticket order. Examples of variable information collected by format manager module 121 include the non-stylistic attributes of a ticket order, such as the price, size, SKU and/or shipping information associated therewith.
  • Format manager module 121 also retrieves help text, prompts and other information relating to the ticket order (e.g., field length, min/max characters, and lists of values) and, in turn, provides said data to commerce module 119 in order to facilitate order capture. Further, format manager module 121 provides validation and catalog look-ups, and performs style and position attributes.
  • help text e.g., field length, min/max characters, and lists of values
  • format manager module 121 provides validation and catalog look-ups, and performs style and position attributes.
  • variable and non-variable information is used by format manager 121 to generate web-retrievable ticket images that can be proofed by the customer through commerce module 119.
  • the ticket images are provided on dynamic screens which therefore allow for the customer to make immediate modifications.
  • format manager module 121 provides GOCA 113 with print-from-the-web (PFTW) capabilities, whereby a client located anywhere globally can design tickets using dynamic, web- enabled proofing screens.
  • PFTW print-from-the-web
  • a physical ticket proof i.e., a ticket sample
  • a physical ticket proof may be sent to the customer for review, if necessary.
  • System 111 permits graphic images to serve as variable information for a particular ticket order.
  • System 111 allows the customer to interactively replace an image provided on a ticket proof.
  • Information entered by the customer may identify the image directly (e.g., with an image file number), or indirectly (i.e., wherein the system generates the graphic image in response to other variable information provided by the customer, based upon rules in format manager module 121 ).
  • a change of Style Number identifying types of shoes causes a graphic product image to change from a high-heel shoe to a golf shoe.
  • a "color by size” color bar may serve as variable information for a particular ticket order.
  • a horizontal color bar may be provided on a price ticket to serve as a marker for the size of the article, wherein each size (small, medium, large, etc.) is represented by a particular color that is assigned using industry standards.
  • This variable graphic image capability supports both the first paradigm of identification media, wherein stylistic attributes are highly constrained, and the second paradigm wherein customers are given more stylistic freedom.
  • Order Management relates to the means by which a ticket order is processed for ticket production. As seen most clearly in Fig. 5, the process by which a ticket order is processed for ticket production includes the following steps.
  • the ticket order is released from order management module 125 to manufacturing module 131 for print planning.
  • manufacturing module 131 oversees the process of printing (i.e., filling) the ticket orders.
  • manufacturing module 131 provides order management module 125 with the frequent updates on the status of the pending ticket order.
  • Financial information relating to the ticket order e.g., invoice number, purchase order number
  • ordermanagemant module 125 tofinancials module 135 for management.
  • order information used for tagging and packing purposes (e.g., item, customer, shipment and/or purchase order data) is released from order management module 125 to warehouse management module 133.
  • warehouse management module 133 manages the processes of affixing the tickets to their corresponding articles, packaging the tagged products and generating advanced shipping notifications (ASN) relating thereto.
  • warehouse management module 133 then releases the advanced shipping notification (ASN) information back to order management module 125.
  • ASN advanced shipping notification
  • Manufacturing Management relates to the means by which a ticket order is released for printing. As seen most clearly in Figs. 2 and 6, the process by which a ticket order is released for printing includes the following steps: (1) As detailed above, order management module 125 releases the ticket order to manufacturing module 131 for processing, the ticket order including at least some of the following information: the item number, customer number and order number associated therewith.
  • Batch manager module 129 generates print job orders which, in turn, are released to format manager module 121 in order to generate detail specific print streams. As can be appreciated, the particular print streams are created to render the printing process more efficient and thereby more cost-effective. The print streams are then released to print manager module 137 by format manager module 121.
  • Manufacturing module 131 additionally releases financial information relating to the print job order to financials module 135.
  • Information released to the financials module 135 includes, among other things, purchase order information, labor costs and inventory valuation (e.g., Raw, WIP, etc.).
  • the financials module 135 sends back to manufacturing module 131 a vouchered purchase order.
  • Manufacturing module 131 additionally releases inventory information to warehouse management module 133 which utilizes the inventory information for warehouse management purposes.
  • order management module 125 During the actual printing process (to be described in detail below), status of the print job is received by order management module 125 from print manager module 137. In this manner, order management module 125 can effectively manage the status of the released print order.
  • Print Management relates to the means by which a released ticket order is printed at print center 115. It should be noted that, by decoupling the print management process from the manufacturing management process described above, the printing process can be standardized such that printing devices can be readily added, removed and/or replaced without compromising either process. In fact, multiple print centers 115 (each having multiple different printers, such as digital, offset and/or thermal printers) can interface with GOCA 113 to provide a wide range of printing capabilities at a wide variety of different geographic locations. As seen most clearly in Figs. 2 and 7, the process by which a print job is executed includes the following steps:
  • a print job order which details the specific print streams that are to be executed, is released from format management module 121 to print manager module 137 via the internet 117 or other similar network.
  • print manager module 137 manages the release of the print job orders. Specifically, print manager module 137 oversees the print screen queuing for multiple printer types and releases the print screen data streams to applicable printer interfaces.
  • Printer interfaces may include one or more of the following: (a) printer software; (b) pre-press software; and (c) direct interface with the printer. Furthermore, if printer 139 utilizes printing plates, print manager module 137 releases the print stream to pre-print software that manages the generation of printing plates at pre-press 141.
  • Print manager module 137 additionally provides order management module 125 with periodic status information relating to the released print job orders.
  • Financials Management relates to the means by which financial documents relating to a ticket order is processed. As seen most clearly in Fig. 8, the process by which financial documents are processed includes the following steps:
  • manufacturing module 131 releases financial information relating to a job order to financials module 135.
  • the types of information released to financials module 135 include purchase order information, labor costs and inventory valuation (e.g., Raw, WIP, etc.). Upon the receipt of this information, financials module 135 sends back to manufacturing module 131 a vouchered purchase order.
  • warehouse management module 133 provides financials module 135 with purchase order information relating to the tickets, such as purchase order receipts and inventory valuation (FG).
  • Warehouse Management relates to the management of the process in which generated tags are affixed to products and then packaged in compliance with client- specified packing instructions. As seen most clearly in Fig. 9, the process by which warehouse management module 133 controls the packing and shipping of tagged articles includes the following steps:
  • warehouse management module 133 releases financial information relating to the packaged and shipped articles (e.g., purchase order receipts, inventory valuation (FG)) to financials module 135.
  • financial information relating to the packaged and shipped articles e.g., purchase order receipts, inventory valuation (FG)
  • Data Storage relates to the means by which relevant ticket order information is aggregated within a globally accessible database 143.
  • a standard integration framework module 145 collects data from GOCA 113 in near real-time.
  • integration framework module 145 is designed to receive data from any other affiliated ticketing systems.
  • integration framework module 145 serves to collect data from GOCA 113aswell as any legacy ticketing service systems (i.e., systems prior to GOCA 113) in order to create a single, comprehensive and all-encompassing database 143, which is highly desirable.
  • Integration framework module 145 is based on service-oriented architecture (i.e., a collection of services that communicate with one another and which are self- contained in nature) and business process management (i.e., a set of activities which organizations can perform to either optimize their business processes or adapt them to new organizational needs).
  • service-oriented architecture i.e., a collection of services that communicate with one another and which are self- contained in nature
  • business process management i.e., a set of activities which organizations can perform to either optimize their business processes or adapt them to new organizational needs.
  • integration framework module 145 is in the form of a Yantra Service Definition Framework.
  • Integration framework module 145 standardizes data as it is collected and, in turn, stores the standardized data in database 143 in near real-time.
  • Database 143 preferably includes an operational data store (ODS), which is a temporary, or interim, database that stores time sensitive operational data that is to be accessed quickly and efficiently (e.g., data received within the last 30-60 days), and a data warehouse, which is a long-term database that stores historical data (i.e., data received over a period of years).
  • ODS operational data store
  • a global visibility module 147 is a web-based application that is connected to database 143, global visibility module 147 serving to organize business information for participants of the supply chain through a single user interface (i.e., "single sign- on").
  • global visibility module 147 provides global access to pertinent business information (order info/status, inventory, sales numbers, etc.) to authorized personnel.
  • Global visibility module 147 is preferably provided using a WebSphere Portal and provides windows into disparate information systems, like PeopleSoft and Yantra.
  • a global reporting module 149 is similarly a web-based application that is connected to database 143.
  • Global reporting module 149 is preferably provided by Hyperion Performance Suite and makes the following types of reports available for review via the internet 117: (i) sales data (by product and customer); (ii) inventory data; (iii) service metrics; (iv) profitability information (by product and customer); (v) W
  • process 211 provides a customer of the retail supply chain with (1) interactive customer ticket proofing/design, (2) globally visible ticket order information, and (3) printer-neutral management of variable ticket data, each of the aforementioned features serving as principal novel features of the present invention.
  • Process 211 commences when a ticket order placed by the customer is electronically captured into GOCA 113 through the web-based storefront (i.e., commerce module 119), said order capture step being represented generally by reference numeral 213.
  • the order is preferably electronically received by commerce module 119.
  • the order may be placed via alternative means of communication ⁇ such as by FAX, email, telephone, etc.) and in an additional step manually keyed into commerce module 119 by customer service representatives for GOCA 113 (e.g., through the main storefront in commerce module 119 orthrough a specially-designed customer service storefront in commerce module 119).
  • the template for the particular style of ticket to be printed is located in GOCA 113.
  • commerce module 119 redirects (i.e., transfers) the ticket order to format manager module 121 for validation; then if the ticket order is validated, the order is transferred to order management module 125.
  • ticketing services bureau 113 utilizes specified modules to generate a dynamic, on-screen ticket proof that can be reviewed by the client globally via the internet 117, the generation of said dynamic, on-screen ticket proof being identified generally by reference numeral 215.
  • format manager module 121 serves to, among other things, retrieve any variable information associated with the tag proof, such as price, size, style, "color by size", etc.
  • a web-based ticket proof is generated which the client can review through commerce module 119. With the ticket proof generated, the customer is then afforded the opportunity to determine whether any changes to the proof are required, said determination step being represented generally by reference numeral 217.
  • the client can edit the variable data of the on-line ticket proof via commerce module 119 as a screen that passes into the format manager module 121 , said editing step being identified generally by reference numeral 219.
  • any changes made with respect to the ticket proof in step 219 are reflected in the on-screen image of the tag in real-time.
  • the customer is instantly provided with an on-screen image of the edited proof which, in turn, can be examined to ascertain whether any additional editing is required.
  • the customer is able to interactively design a web-based proof which will accurately depict the particular tag to be produced as part of the initial ticket order.
  • this ability of GOCA 113 to provide its customers with a dynamic means of interactive tag review serves as a principal novel feature of the present invention.
  • identification media with relatively standardized formatting attributes (e.g., font type, font size, printed matter layout, etc.), such as conventional price tickets and shipping labels, and (2) identification media with relatively unique formatting attributes, such as fabric labels or other similar types of media which allow for the customer to implement item-specific design characteristics thereto.
  • relatively standardized formatting attributes e.g., font type, font size, printed matter layout, etc.
  • identification media with relatively unique formatting attributes such as fabric labels or other similar types of media which allow for the customer to implement item-specific design characteristics thereto.
  • system 111 preferably affords the customer to interactively modify non-stylistic attributes associated with a ticket, such as size, style, price, description code, country of origin, etc.
  • non-stylistic attributes associated with a ticket such as size, style, price, description code, country of origin, etc.
  • stylistic attributes associated with a ticket such as font characteristics (e.g., font type, font size, bold/italic/underline, scale, etc.) and layout (e.g., rotation, margins, field positioning, etc.), which are typically "givens" for a particular ticket type (e.g., conventional price tickets).
  • system 111 preferably enables a customer to interactively modify multiple attributes associated with a ticket including, inter alia, the stylistic attributes associated with a ticket, such as font characteristics (e.g., font type, font size, bold/italic/underline, scale, etc.) and layout (e.g., rotation, margins, field positioning, etc.).
  • font characteristics e.g., font type, font size, bold/italic/underline, scale, etc.
  • layout e.g., rotation, margins, field positioning, etc.
  • variable ticket information associated with the ticket proof is sent from format manager module 121 to commerce module 119 which, in turn, sends it to order management module 125 where the information is bundled together with the original ticket order data, said sending step being identified generally by reference numeral 221 in Fig. 10.
  • the visual (i.e., digital) component of the approved tag can be retained within commerce module 119 (i.e., for future review by authorized parties).
  • order management module 125 oversees the batching process for the ticket order, said step being identified by reference numeral 223 in Fig. 10. Specifically, order management module 125 directs batch manager module 129 to manage order batching (i.e., grouping together similar ticket orders in order to minimize printing costs). In addition, format manager module 121 directs optimization manager module 127 to optimize the layout for printing by (1 ) determining the number of tags for each order that should be printed based on the layout from format manager module 121, and (2) minimizing the number of printing plates that will be needed.
  • batch manager module129 then transmits a print job order (in compliance with the batching process executed in step 223) to format manager module 121 , the transmission step being identified generally by reference numeral 225.
  • format manager 121 calls optimization manager 127, if applicable, and W
  • order management module 125 determines which print center 115 is most aptly suited to generate the tickets and, in accordance therewith, format manager module 121 creates the output file in the particular format and layout required by the selected (i.e. , target) printer 139.
  • a very useful feature of the present ticket order processing system is that if it is necessary to change the printer or layout, format manager 121 automatically generates the output data file.
  • Order management module 125 then instructs manufacturing module 131 to process the print order, said instruction step being identified by reference numeral 227.
  • format manager module 121 When printing is to be performed using non-digital printing means (e.g., offset printing, flexographic printing, etc.), format manager module 121 produces a completed output file (e.g., a .pdf-type file) which includes, inter alia, page size, layout, margins, columns, number of ups, all graphics, fonts and other similar items needed for the printing press. It is also important to note that format manager module 121 separates this information into distinct plate layers forthe printing device, thereby resulting in significant time and cost saving advantages.
  • a completed output file e.g., a .pdf-type file
  • the output file generated by the format manager module 121 is run through the software for producing the physical plates used by the offset printing press. It is to be understood that format manager module 121 handles the process of displaying which batches/orders are ready to be released (including due dates, number of plates, colors, quantity, etc.) and then, upon direction of the operator, releases or routes the .pdf file to the plate making software. For digital printing processes, a similar output file is released by format manager module 121 directly to the printer or to any other front-end software that is needed, as will be described further below.
  • format manager module 121 Based on instructions from order management module 125, format manager module 121 then releases the output file as an electronic data stream formatted for the target printer 139, the output file being released to the print manager module 137 of the selected print center 115 as part of a designated print stream, said releasing step being identified generally by reference numeral 229.
  • format manager module 131 utilizes an AS/2-type protocol for optimized security and guaranteed delivery.
  • Print manager module 137 then manages all of the various print streams received from ticketing services bureau 113, said management step being identified generally by reference numeral 231. Specifically, print manager module 137 oversees the print screen queuing for multiple printer types and releases the print screen data streams to applicable printer interfaces, printer interfaces including one or more of the following: (a) printer software, (b) pre-press software, and (c) direct interface with the printer. Furthermore, if printer 139 utilizes printing plates, print manager module 137 releases the print stream to pre-print software that manages the generation of printing plates at pre-press 141. It should be noted that, because print manager module 137 and format manager module 121 are separate yet interrelated modules, system 111 is able to support a wide variety of different printers, which is highly desirable.
  • a notification relating to the ganged orders is sent back from print manager module 137 to order management module 125 in order to allow for the real-time tracking of relevant data with respect tp the pending print order (e.g., status, labor information, etc), said step being identified generally by reference numeral 233.
  • warehouse management module 133 is instructed by order management module 125 to manage the tagging and packing operations at manufacturing facility 19, said step being identified generally by reference numeral 235. It should be noted that warehouse management module 133 provides pertinent packing information (e.g., advanced shipping notifications (ASNs)) to order management module 125 which are, in turn, globally retrievable by authorized participants of the supply chain fortracking purposes, which is highly desirable.
  • ASNs advanced shipping notifications
  • invoices may be sent by order management module 125 to financials module 135 for processing.
  • the embodiment, shown in the present invention is intended to be merely exemplary and those skilled in the art shall be able to make numerous variations and modifications to it without departing from the spirit of the present invention.
  • modules in ticketing services bureau 113 could be added, removed and/or combined without departing from the spirit of the present invention.

Abstract

La présente invention concerne un système conçu pour gérer la production de tickets au détail en fonction d'une commande de ticket. Ce système comprend une société de services d'émission de ticket qui est conçue pour recevoir la commande de ticket, ainsi qu'un centre d'impression qui permet d'imprimer des tickets en fonction de la commande de ticket. Le système comprend également un client qui est en connexion avec la société de services d'émission de ticket via un réseau électronique. Faisant partie d'un processus de vérification de ticket interactif, le client est en mesure de récupérer par voie électronique une preuve de ticket sur écran à partir de la société de services d'émission de ticket et, si nécessaire, de modifier de façon dynamique la preuve de ticket sur écran en temps réel. La société de services d'émission de ticket produit ensuite un fichier de données de sortie sur la base de la commande de ticket originale, de la preuve de ticket sur écran éditée et de caractéristiques d'impression de l'imprimante qui va exécuter la commande de ticket. De cette manière, le centre d'impression utilise le fichier de données de sortie afin de produire des tickets qui ressemblent fortement à la preuve de ticket sur écran approuvée par le client.
EP06844744A 2005-12-01 2006-12-01 Systeme et procede pour gerer une commande de ticket Ceased EP1966747A4 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP13178374.8A EP2660758A1 (fr) 2005-12-01 2006-12-01 Système et procédé pour gérer une commande de ticket

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US74136105P 2005-12-01 2005-12-01
PCT/US2006/046104 WO2007064939A2 (fr) 2005-12-01 2006-12-01 Systeme et procede pour gerer une commande de ticket

Publications (2)

Publication Number Publication Date
EP1966747A2 true EP1966747A2 (fr) 2008-09-10
EP1966747A4 EP1966747A4 (fr) 2010-10-27

Family

ID=38092853

Family Applications (2)

Application Number Title Priority Date Filing Date
EP06844744A Ceased EP1966747A4 (fr) 2005-12-01 2006-12-01 Systeme et procede pour gerer une commande de ticket
EP13178374.8A Ceased EP2660758A1 (fr) 2005-12-01 2006-12-01 Système et procédé pour gérer une commande de ticket

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP13178374.8A Ceased EP2660758A1 (fr) 2005-12-01 2006-12-01 Système et procédé pour gérer une commande de ticket

Country Status (4)

Country Link
US (2) US7472828B2 (fr)
EP (2) EP1966747A4 (fr)
CN (2) CN101421699B (fr)
WO (1) WO2007064939A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10726363B2 (en) 2016-06-16 2020-07-28 International Business Machines Corporation Ticket event modification for a problem tracking system ticket
US11080636B1 (en) 2020-11-18 2021-08-03 Coupang Corp. Systems and method for workflow editing

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001059696A2 (fr) * 2000-02-09 2001-08-16 Moore North America, Inc. Imagerie de document a contenu statique et a donnees variables
CA2346215A1 (fr) * 2000-05-05 2001-11-05 Xerox Corporation Format de fichier a reimpression rapide utilisant des etiquettes privees pour produire des documents reimprimables pouvant etre visualises et edites a l'aide d'outils ordinaires
US20050105129A1 (en) * 2003-11-13 2005-05-19 Canon Kabushiki Kaisha Image forming apparatus, image processing system, method of processing a job, method of controlling a job, and computer readable storage medium including computer-executable instructions

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5930810A (en) * 1995-08-09 1999-07-27 Taylor Corporation Printing system with pre-defined user modifiable forms and local and remote printing
US6442526B1 (en) * 1995-09-06 2002-08-27 The Sabre Group, Inc. System for corporate travel planning and management
US6999936B2 (en) * 1997-05-06 2006-02-14 Sehr Richard P Electronic ticketing system and methods utilizing multi-service visitor cards
US6247011B1 (en) * 1997-12-02 2001-06-12 Digital-Net, Inc. Computerized prepress authoring for document creation
US6980964B1 (en) * 2000-07-27 2005-12-27 Canon Kabushiki Kaisha Virtual print market place
CN1341904A (zh) * 2000-09-04 2002-03-27 线上丝路图书股份有限公司 先接单后印刷的弹性出版系统与方法
JP2002133133A (ja) * 2000-10-19 2002-05-10 Sony Corp 画像印刷受注システム及び画像印刷受注方法
US20050237578A1 (en) * 2002-07-10 2005-10-27 Konica Minolta Holdings, Inc. Print order slip issuing device and print generation system
US7548334B2 (en) * 2003-10-15 2009-06-16 Canon Kabushiki Kaisha User interface for creation and editing of variable data documents
US20050162689A1 (en) * 2004-01-23 2005-07-28 Eastman Kodak Company System and method for communicating with printers using web site technology
US20050209892A1 (en) * 2004-03-19 2005-09-22 Miller Jonathan K [Automated system and method for providing accurate, non-invasive insurance status verification]
CN100578541C (zh) * 2004-07-06 2010-01-06 洪朝阳 一种票务系统及使用方法
CN1614615A (zh) * 2004-12-07 2005-05-11 北京邮电大学 一种通过移动通信终端购买有价票据的方法及系统
US7607577B1 (en) * 2005-10-19 2009-10-27 Amazon Technologies, Inc. Method and system for analyzing inventory purchasing opportunities with respect to inventory health

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001059696A2 (fr) * 2000-02-09 2001-08-16 Moore North America, Inc. Imagerie de document a contenu statique et a donnees variables
CA2346215A1 (fr) * 2000-05-05 2001-11-05 Xerox Corporation Format de fichier a reimpression rapide utilisant des etiquettes privees pour produire des documents reimprimables pouvant etre visualises et edites a l'aide d'outils ordinaires
US20050105129A1 (en) * 2003-11-13 2005-05-19 Canon Kabushiki Kaisha Image forming apparatus, image processing system, method of processing a job, method of controlling a job, and computer readable storage medium including computer-executable instructions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2007064939A2 *

Also Published As

Publication number Publication date
CN101421699B (zh) 2014-10-08
US20090125416A1 (en) 2009-05-14
EP1966747A4 (fr) 2010-10-27
US7472828B2 (en) 2009-01-06
US20070145111A1 (en) 2007-06-28
US7926715B2 (en) 2011-04-19
WO2007064939A3 (fr) 2008-12-31
CN101356496A (zh) 2009-01-28
CN101421699A (zh) 2009-04-29
EP2660758A1 (fr) 2013-11-06
WO2007064939A2 (fr) 2007-06-07

Similar Documents

Publication Publication Date Title
US7249322B2 (en) E2 automobile dealership information management system
US20050114193A1 (en) Strategic sourcing for packaging material procurement using centralized packaging data management system
US20020069096A1 (en) Method and system for supplier relationship management
EP2605201A1 (fr) Procédé de traitement d'une commande de billet
US20070078725A1 (en) Integrated customer fulfillment management
JP2002203153A (ja) オーダーメイド商品の販売システム、オーダーメイド商品の販売方法、オーダーメイド商品の販売に用いられるサーバ、および、記録媒体
US7789301B2 (en) System and method of managing a ticket order
US6903839B1 (en) Apparatus for washing of graphic image files
US7926715B2 (en) System and method of managing a ticket order
CN101491077B (zh) 将数字印刷机与基于板的印刷台的色彩特性相匹配的方法
US20040153332A1 (en) Printed materials procurement system
JP2002203152A (ja) 電子商店管理システム、電子商店管理方法、及び記録媒体
US7843615B2 (en) Method of matching a digital printing press with the color characteristics of a plate-based press platform
US20030050958A1 (en) Supplier/reseller interaction
JP4741724B2 (ja) 伝票値札発行方法及び伝票値札発行システム並びに伝票値札発行装置
EP2166504A1 (fr) Procédé et dispositif pour le traitement automatique de données de marchandises
Abdinnour-Helm Time-based competition through better customer service
EP2039146B1 (fr) Procédé d'harmonisation d'une presse à imprimer numérique avec les caractéristiques couleurs d'une plate-forme de presse à plaque
US20030050847A1 (en) Supplier/reseller interaction
TW518496B (en) Management method and system of delivering goods
US20090166416A1 (en) Inventory system and process
US20030236678A1 (en) Automated process for pharmaceutical printed component production
JP2001338190A (ja) 贈答品の受注処理方法
JPH0772997A (ja) 情報印字方法
WO2001052114A1 (fr) Systeme de generation de taches de production d'impression

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK RS

R17D Deferred search report published (corrected)

Effective date: 20081231

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 7/08 20060101AFI20090325BHEP

17P Request for examination filed

Effective date: 20090630

RBV Designated contracting states (corrected)

Designated state(s): DE GB

DAX Request for extension of the european patent (deleted)
RBV Designated contracting states (corrected)

Designated state(s): DE GB

A4 Supplementary search report drawn up and despatched

Effective date: 20100928

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 10/00 20060101AFI20100922BHEP

17Q First examination report despatched

Effective date: 20110719

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBX Invitation to file observations in appeal sent

Free format text: ORIGINAL CODE: EPIDOSNOBA2E

APBZ Receipt of observations in appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNOBA4E

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: AVERY DENNISON RETAIL INFORMATION SERVICES LLC

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20221124