Source: http://www.google.com/patents/US20080262948?dq=2040248
Timestamp: 2015-07-06 23:25:22
Document Index: 154379811

Matched Legal Cases: ['Application No. 60', 'art 120', 'art 120', 'art 120', 'arts 120', 'art 120', 'art 120', 'art 120', 'art 120', 'art 120', 'art 120', 'art 120', 'art 120']

Patent US20080262948 - Alert distribution and management system and returns module - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA method for managing a returns process in response to product alerts is provided. The method includes receiving an alert related to a product. The method also includes processing the alert into an alert repository. The method further includes retrieving product data based on the alert. The method further...http://www.google.com/patents/US20080262948?utm_source=gb-gplus-sharePatent US20080262948 - Alert distribution and management system and returns moduleAdvanced Patent SearchPublication numberUS20080262948 A1Publication typeApplicationApplication numberUS 12/071,101Publication dateOct 23, 2008Filing dateFeb 15, 2008Priority dateFeb 16, 2007Also published asUS8190449, WO2008103274A2, WO2008103274A3Publication number071101, 12071101, US 2008/0262948 A1, US 2008/262948 A1, US 20080262948 A1, US 20080262948A1, US 2008262948 A1, US 2008262948A1, US-A1-20080262948, US-A1-2008262948, US2008/0262948A1, US2008/262948A1, US20080262948 A1, US20080262948A1, US2008262948 A1, US2008262948A1InventorsPatrick Charles Grady, Richard Hardy Fiddleman, Robert Irwin Patt-CornerOriginal AssigneePatrick Charles Grady, Richard Hardy Fiddleman, Robert Irwin Patt-CornerExport CitationBiBTeX, EndNote, RefManPatent Citations (6), Referenced by (5), Classifications (17), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetAlert distribution and management system and returns module
US 20080262948 A1Abstract
A method for managing a returns process in response to product alerts is provided. The method includes receiving an alert related to a product. The method also includes processing the alert into an alert repository. The method further includes retrieving product data based on the alert. The method further includes associating the product data with the alert. The method further includes facilitating a return of the product to a vendor using the product data. The method further includes receiving data in response to the return of the product. The method further includes providing an actionable display including the product data, the data in response to the return, and data related to a return action.
receiving an alert related to a product; processing the alert into an alert repository; retrieving product data based on the alert; associating the product data with the alert; facilitating a return of the product to a vendor using the product data; receiving data in response to the return of the product; and providing an actionable display including the product data, the data in response to the return, and data related to a return action. 2. The method of claim 1, wherein retrieving product data from a product repository further comprises:
retrieving purchase history and inventory data of the product from a product repository. 3. The method of claim 2, wherein the purchase history and inventory data consists of one of a vendor name, a vendor ID, a purchase order number, a number of products in stock, a location of the products, and a stock identifier.
notifying the vendor of a return of the product; decrementing an inventory by a number of the product returned; determining whether the inventory falls below a predetermined level; reordering the inventory upon a determination that the inventory falls below the level; and preparing an invoice for the vendor. 5. The method of claim 4, wherein notifying the vendor of a return of the product further comprises:
reporting the product to indicate a forthcoming return of the product. 6. The method of claim 1, wherein facilitating the return of the product further comprises:
requesting a return of the product from the vendor; and requesting a credit from the vendor for the return. 7. The method of claim 6, wherein requesting a return further comprises:
requesting a return authorization number from the vendor. 8. The method of claim 1, wherein the data in response to the return comprises return disposition information and shipment information, the return disposition information comprising what is to be done with the product, and the shipment information comprising a return authorization number from the vendor.
9. The method of claim 1, wherein the return action is one of a refund, a reimbursement, and a replacement.
10. The method of claim 9, wherein the data related to the return action includes financial activity type, credit taken, and credit number.
an alert component that
receives an alert related to a product; and
processes the alert into an alert repository; and
a return component that
retrieves product data based on the alert;
associates the product data with the alert;
facilitates a return of the product to a vendor using the product data;
receives data in response to the return of the product; and
provides an actionable display including the product data, the data in response to the return, and data related to a return action.
12. The system of claim 11, wherein the product data consists of one of a vendor name, a vendor ID, a purchase order number, a number of products in stock, a location of the products, and a stock identifier.
13. The system of claim 11, wherein the system further comprises an inventory component, and
wherein the return component facilitates the return of the product by enabling the inventory component to: notify the vendor of a return of the product; decrement an inventory by a number of the product returned; determine whether the inventory falls below a predetermined level; reorder the inventory upon a determination that the inventory falls below the level; and prepare an invoice for the vendor. 14. The system of claim 11, wherein the return component facilitates the return of the product by:
requesting a return of the product from the vendor; and requesting a credit from the vendor for the return. 15. The system of claim 11,
wherein the data in response to the returns comprises return disposition information and shipment information, the return disposition information comprising what is to be done with the product, and the shipment information comprising a return authorization number from the vendor, and wherein the return action is one of a refund, a reimbursement, and a replacement. 16. The system of claim 15, the data related the return action includes data related to financial activity type, credit taken, and credit number.
17. A computer program product, tangibly embodied in computer-readable medium, the computer program product being operable to cause data processing apparatus to perform operations comprising:
receiving an alert related to a product; processing the alert into an alert repository; retrieving product data based on the alert; associating the product data with the alert; facilitating a return of the product to a vendor using the product data; receiving data in response to the return of the product; and providing an actionable display including the product data, the data in response to the return, and data related to a return action. 18. The computer program product of claim 17, wherein the product data consists of one of: a vendor name, a vendor ID, a purchase order number, a number of products in stock, a location of the products, and a stock identifier.
notifying the vendor of a return of the product; decrementing an inventory by a number of the product returned; determining whether the inventory falls below a predetermined level; reordering the inventory upon a determination that the inventory falls below the level; and preparing an invoice for the vendor. 20. The computer program product of claim 17, wherein facilitating the return of the product further comprises:
requesting a return of the product from the vendor; and requesting a credit from the vendor for the return. Description
This application claims the benefit of the filing date of U.S. Provisional Application No. 60/901,659 filed Feb. 16, 2007, incorporated in its entirety herein by reference.
The present invention relates generally to an enterprise application. More particularly, the present invention relates to managing a returns process of recalled products in an alert distribution and management system.
When a manufacturer determines that a product is defective, the manufacturer may issue an alert (e.g., a recall notice, field correction, repair instructions, etc.) to notify customers to stop using the product, return the product, etc. Issuing an alert is costly to a manufacturer because an alerted product may need to be replaced or fully refunded, but it often limits liability for a manufacturer and prevents further damage to the manufacturer's corporate image. A product alert is not, however, easy to learn about because, for example, a manufacturer may not always publicize an alert. A manufacturer may merely notify a government agency, and it is often a consumer group that publicizes an alert that the group learns from the agency. Further, a customer may have hundreds or thousands of products to search for alerts on.
An alert distribution and management system with a returns module using information technology may alleviate the alert and returns management problems. One example of an alert distribution and management system may be the Risk and Safety Management Alert System (RASMAS™) with a returns module from Noblis. The alert distribution and management system with the returns module may provide organizations with a new infrastructure for alert and returns management.
Reference will now be made in detail to the invention, examples of which are illustrated in the accompanying drawings. Implementations set forth in the following description do not represent all implementations consistent with the claimed invention. Instead, they are merely some examples consistent with certain aspects related to the invention. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
FIG. 1 illustrates an exemplary alert distribution and management system 110 incorporating a returns module 120. In one embodiment, returns module 120 may include returns module part 120 a, returns module part 120 b, and returns module part 120 c As shown in FIG. 1, system 110 may include alert processor 112, database 114, web application 116, and interface component 118. Alert processor 112, database 114, web application 116, and interface component 118 may include any number of computers, devices, hardware, and/or mainframe located anywhere and distributed among multiple locations. Alert processor 112, database 114, web application 116, and interface component 118 may also include operating systems, such as Microsoft Windows™, or any UNIX derived operating system, such as Linux�, Solaris™, and FreeBSD. In this embodiment, returns module 120 may have multiple parts 120 a, 120 b, and 120 c distributed throughout system 110. For example, as shown in FIG. 1, part 120 a may run as a part of alert processor 112, part 120 b may run as a part of web application 116, and part 120 c may run as a part of interface component 118. Although FIG. 1 shows that returns module 120 runs as a part of alert processor 112, web application 116, and interface component 118, returns module 120 may be separate from system 110, and may interact with system 110 seamlessly.
Database 114 may include a database management system (DBMS). The DBMS may store and retrieve data from, and manage database 114. To this end, the DBMS may provide services such as transactions and concurrency, indexing, security, and backup and replication. The DBMS may be based on, for example, a relational model, object database model, post-relational database model, hierarchical model, or flat model. In certain embodiments, a DBMS may be implemented as Oracle™ DBMS, IBM's DB2™, Microsoft SQL Server™, PostgresSQL, or MySQL�.
Web application 116 may include a web server. The web server may accept hypertext transfer protocol (HTTP/HTTPS) requests from users, such as users 132, 134, 136, 142, 144, 152, and 154 through network 172, and send HTTP/HTTPS responses back to the users with web pages, which may comprise hypertext markup language (HTML) or extensible markup language (XML) documents and any linked or embedded objects, such as images. For example, the web server may exchange XML-based messages with the users using Simple Object Access Protocol (SOAP) on top of HTTP/HTTPS. In certain embodiments, the web server may be implemented as Apache HTTP Server™, Internet Information Service (IIS)™, Sun Java System Web Server™, or IBM HTTP Server™.
In certain embodiments, web application 116 may include an application server that enables dynamic generation of web pages. For example, web application 116 may employ Java Enterprise Edition (JEE) technologies, such as Java Server Page™ (JSP) and Java Servlet™, to enable dynamic generation of web pages, and a JEE application server, such as IBM's WebSphere™, BEA's WebLogic™, JBOSS™, and JRun™, may be implemented as an application server to support the technologies. Web application 116 may alternatively employ Microsoft .NET Framework™, such as ASP.NET™ to enable dynamic generation of web pages.
Alert subscribing entities 130, 140, and 150 may employ any number of users that may manage and respond to alerts. In certain embodiments, alert subscribing entity 130 may employ users 132, 134, and 136, alert subscribing entity 140 may employ users 142 and 144, alert subscribing entity 150 may employ users 152 and 154, as shown in FIG. 1. In certain embodiments, users 132, 134, and 136 may manage and respond to alerts for all facilities within alert subscribing entity 130 while users 142 and 144 may manage and respond to alert for only one facility within alert subscribing entity 140. In certain embodiments, users 132, 134, and 136 may be charged with a single role in managing and responding to alerts while users 142 and 144 may be charged with multiple roles in managing and responding to alerts. For example, user 142 may be charged with a managing role (“manager”) that may require overseeing alert processing within alert subscribing entity 140. User 142 may also be charged with another role, such as an administrating role (“administrator”) that may require handling administrative tasks, such as entering data into system 110.
User 134 may be charged with a coordinating role (“coordinator”) that may require assigning alerts to a user charged with a responding role (“responder”). For example, in coordinating alerts, user 134 may assign a product recall alert to user 136, who may be a responder. The assignment may require user 136 to handle the alert by disposing of the recalled product. Failure to perform assigned roles may trigger an escalation process as described in greater detail with respect to FIG. 4. Actions that users 132, 134, 136, 142, 144, 152, and 154 may perform through web application 116 and returns module part 120 b may be limited based on the assigned roles. In certain embodiments, however, any of users 132, 134, 136, 142, and 144 may access and perform any actions in returns module part 120 b to manage returns, reimbursements, and replacements processes of the recalled products.
FIG. 3 illustrates an exemplary alert management and coordination assignment process 300. Each facility within alert subscribing entities 130, 140, and 150 may receive a subscribed alert (step 310). A coordinator, such as user 134, may review the subscribed alert to determine whether it requires a responsive action (step 320). Upon review, if user 134 determines that the alert requires no further action (step 320 “No”), user 134 may close the alert (step 360). If user 134 determines that the alert requires a responsive action (step 320 “Yes”), user 134 may assign the alert to a responder, such as user 136 (step 330). User 136 may perform a task or tasks in response to the alert (step 340). For example, user 136 may dispose of any recalled products in response to a product recall alert. After user 136 completes the task(s), user 136 may record actions performed in system 110, e.g., by using web application 116 (step 350). User 134 may then close the alert (step 360). In certain embodiments, users may be notified by an e-mail at the completion of the step. For example, when a responder completes an action in response to an alert, a coordinator may receive an automatic e-mail notification via system 110.
FIGS. 5A-5C depict screen displays of web pages generated and presented by exemplary web application 116 of system 110. A user may log into web application 116 and see a welcome screen, as shown in FIG. 5A. The left column of the welcome screen may display quick links, and the center column of the screen may display alert and recall related news or information. The right column of the screen may display a summary and status of currently open alerts that may require the user's action. For example, for the user “Carl Jones,” an alert status shows that the user is a coordinator for five (5) alerts, with zero (0) alert as a responder or manager. As shown in the legend, colors or other indicators may show delayed or escalated alerts.
On the detailed screen shown in FIG. 5C, the user may see more detailed information about one of the alerts listed on the list screen shown in FIG. 5B. The detailed information may include, in addition to the information shown in the list screen, comments by an alert analyst, source alert type, source type, detailed product information, and work assignments information. The detailed screen may include links to perform several actions, for example, in the left column as shown in FIG. 5C. In certain embodiments, the links may include “ASSIGN RESPONSE,” “REASSIGN COORDINATOR,” “ADD WORK NOTE,” “SEND FYI E-MAIL,” “CLOSE COORDINATION,” and “RETURN INFORMATION” links. The “RETURN INFORMATION” link may direct the user to web pages generated and presented by returns module part 120 b which are described in more detail with respect to FIGS. 9A-9C. Any screens of web application 116 may include a link to web pages generated and presented by returns module part 120 b. FIG. 6 illustrates an exemplary returns process 600. An administrator may review a product alert, for example, by using web application 116 (step 605). The administrator may initiate a returns process in response to the alert (step 610). To this end, the administrator may retrieve purchasing history or inventory data of the alerted product(s) from a database and/or external system 160. The purchasing history and inventory data may include, among others, a product key, product description, model/product number, stock identifiers, facility stock identifiers, original volume, a vendor name or ID, a purchase order number, a number of the products in stock, and locations of the products. The administrator may associate the purchasing history and inventory data with the alert (step 615). To this end, the administrator may enter materials management advice into a returns module 120 based on the purchasing history and inventory data and other available data. The materials management advice may include a number of fields as described in more detail with respect to FIGS. 9B and 10. A coordinator may review the product alert and validate the materials management advice. A coordinator may enter additional advice into a returns module 120.
A responder may acknowledge the product alert (step 620), for example, by printing the product alert with a bar coded alert number. The responder may locate and retrieve the product (step 625). The responder may request a product return and/or credit from a vendor (step 630), for example, by completing a return requisition form. A vendor may be any entity involved in manufacturing and/or distribution of the product. Requesting a product return may further involve requesting a Return Material/Merchandise Authorization (RMA) number. The responder may also scan the product to indicate a product return. If it is determined that the product should be returned (step 640, “Yes”), return information may be entered into returns module 120 (step 650). In certain embodiments, returns module 120 may receive the return information from external system 160. When an RMA number is received from the vendor, shipping information may be entered into returns module 120 (step 652). In certain embodiments, returns module 120 may receive the shipping information from external system 160. The product may then be shipped to the vendor (step 654). If the responder determines that the product should not be returned (step 640 “No”), the responder may destroy the product (step 660). The responder may then record that the product has been destroyed (step 662), for example, by using returns module 120.
FIG. 7 illustrates an exemplary replacement and reimbursement process 700. While performing returns process 600, a responder may indicate a return of the alerted product (step 710), for example, by scanning the alerted product. The indication of return may decrement inventory by a number of the product (step 720). In certain embodiments, the indication of return may be notified to external system 160, and the external system 160 may update its inventory data. If the inventory falls below a par level after the decrement (step 730, “Yes”), the inventory may automatically be reordered (step 735). In certain embodiments, external system 160 may perform the step of reordering the inventory. An invoice may be prepared to receive reimbursement from the vendor (step 740). In certain embodiments, external system 160 may perform the step of preparing the invoice. Information related to the replacement and/or reimbursement may be entered into returns module 120. In certain embodiments, returns module 120 may receive the information from external system 160. A coordinator may verify the information and close the product alert (step 760).
FIGS. 9A-9C depict screen displays of web pages generated and presented by exemplary web application 116 incorporating returns module part 120 b. FIG. 9A depicts a screen display of Tabbed Summary page 820. The screen may display products that are affected by a specific alert. As shown in FIG. 9A, the screen displays three (3) products for Alert #2005020056. For each product, fields such as “Product Key,” “Product Description,” “Model/Product Number,” “Stock Identifiers,” “Volume,” and “Recall ID” of the product may be displayed on the screen. The screen may include sorting and/or filtering mechanisms. As shown in FIG. 9A, the screen allows a user to sort and/or filter based on, for example, facilities, products, and/or activity creation dates. The screen may display more detailed information on returns activities for the products affected by the alert. The screen may use tabs to display more information in a limited area. As shown in FIG. 9A, the screen may include tabs such as “Advice,” “Returns,” “Procurement,” “Financial,” and “Summary” tabs.
When the “Advice” tab is selected, the screen may display the materials management advice received or collected during process 600. The materials management advice may be an instance of Advice class 1020, which is described in more detail with respect to FIG. 10. As shown in FIG. 9A, for each return activity, data such as “Product Key,” “Note,” “Location Description,” “Stock Identifiers,” “Facility Stock ID,” “Locations,” “Volume & Unit Type,” “Purchase Order,” and “Vendor ID/Name” may be displayed when the “Advice” tab is selected. When the “Returns” tab is selected, the screen may display the return information received or collected during processes 600 and/or 700. The return information may be represented as an instance of Return Data class 1030, which is described in more detail with respect to FIG. 10. To this end, any data fields from Base class 1010, and “ReturnDisposition” field may be displayed when the “Return” tab is selected.
When the “Procurement” tab is selected, the screen may display the shipping information received or collected during processes 600 and/or 700. The shipping information may be represented as an instance of Shipment class 1040, which is described in more detail with respect to FIG. 10. To this end, any data fields from Based class 1010, and “RMANumber,” “VendorAuthorizingIndividual,” “ReturnsAuthorizingIndividual,” and “ReasonForCredit” fields may be displayed when the “Procurement” tab is selected. When the “Financial” tab is selected, the screen may display the financial information received or collected during processes 600 and/or 700. The financial information may be represented as an instance of Finances class 1050, which is described in more detail with respect to FIG. 10. To this end, any data fields from Base class 1010, and “Credit Taken,” “CreditNumber,” and “FinancialActivityType” fields may be displayed when the “Financial” tab is selected. When the “Summary” tab is selected, the screen may display a summary of the information on the returns activities. The materials management advice, returns information, shipping information, and financial information may be reported or presented to a user in any other form to provide a better understanding of returns processes and to enable user to manage returns, reimbursements, and replacements processes.
Tabbed Summary page 820 may provide a number of actions that a user may perform in managing returns, reimbursements, and replacements processes. For example, a user may delete a return activity from the page using “Delete” link as shown in FIG. 9A. A user may also edit an Advice, Return, Shipping, and Financial Record using “Edit” link as shown in FIG. 9A. In certain embodiments, a deleted record or prior record before update may be retained for audit. From Tabbed Summary page 820, a user may be directed to Edit Product Keys page 825 to edit a product key using the “Edit Product Key” tab. A user may also be directed to Create Advice Record page 830, Create Return Record page 840, Create Shipment Record page 850, and Create Finance Record page 860 using “Add Advice Record,” “Add Return Record,”, “Add Shipping Record,” and “Add Financial Record” links, respectively.
FIG. 9B depicts a screen display of Create Advice Record page 830. The screen may display all products for which a new Advice Record may be created. As shown in FIG. 9B, the screen displays three (3) products for Alert #2005020056. For each product, data such as “Product Key,” “Product Description,” “Model/Product Number,” “Stock Identifiers,” “Volume,” and “Recall ID” of the product may be displayed on the screen. A user may select a product for which a new Advice Record will be created. A user may then provide information, such as “Local Product Description,” “Local Model/Product Number,” “Note,” “Stock Identifiers (comma separated list),” “Stock Identifier (text),” “Facility Stock ID (comma separated list),” “Facility Stock ID (text),” “Location,” “Volume of Units Affected,” “Types of Unit,” “Purchase Order,” “Vendor ID,” “Vendor Name,” and “Facilities” in the form provided on the screen. An administrator or coordinator may use the form on the screen to enter materials management advice into returns module 120 as described with respect to step 615 of process 600.
FIG. 9C depicts a screen display of Create Finance Record page 860. The screen may display all products for which a new Financial Record may be created. As shown in FIG. 9C, the screen displays three (3) products for Alert #2005020056. For each product, data such as “Product Key,” “Product Description,” “Model/Product Number,” “Stock Identifiers,” “Volume,” and “Recall ID” of the product may be displayed on the screen. A user may select a product for which a new Financial Record will be created. A user may then provide information, such as “Local Product Description,” “Local Model/Product Number,” “Note,” “Credit Taken,” “Credit Number,” “Financial Activity Type,” and “Facilities” in the form provided on the screen. The form on the screen may be used to enter financial information as described with respect to step 670 of process 600 and step 750 of process 700.
FIG. 10 depicts a class diagram of exemplary classes available in returns module 120. Returns module 120 may include Base class 1010. Base class 1010 may include a number of data fields, such as “ParentID,” “ItemID,” “Alert ID,” “ID,” “ModCount,” “ModelProductNo,” “PurchaseOrder,” “VendorName,” “InternalVendorID,” “ProductKey,” “ProductDescription,” “Facilities,” “Note,” “AlertStockIdentifiersCommaSeparatedList,” “AlerStockIdentifiersFreeFormat,” “FacilityStockIdentifiersCommaSeparatedList,” “FacilityStockIdentifiersFreeFormat,” “NumberOfUnitsAffected,” “UnitTypes,” “Locations,” “LogicalCreation Date,” and “LastUpdateDate” fields.
Return Data class 1030 may include “ReturnDisposition” field. Return Data class 1030 may be used to capture and hold the data received or collected using Create Return Record page 840 and/or Update Return Record page 845 during processes 600 and 700. Shipment class 1040 may include “RMANumber,” “VendorAuthorizingIndividual,” “ReturnsAuthorizingIndividual,” and “ReasonForCredit” fields. Shipment class 1040 may be used to capture and hold the data received or collected using Create Shipment Record page 850 and/or Update Shipment Record page 855 during processes 600 and 700. Finances class 1050 may include “CreditTaken,” “CreditNumber,” and “FinancialActivityType” fields. Finance class 1050 may be used to capture and hold the data received or collected using Create Finance Record page 860 and/or Update Finance Record page 865 during processes 600 and 700.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6115690 *Dec 22, 1997Sep 5, 2000Wong; CharlesIntegrated business-to-business Web commerce and business automation systemUS20010056359 *Feb 8, 2001Dec 27, 2001Abreu Marcio MarcSystem and method for communicating product recall information, product warnings or other product-related information to users of productsUS20020156797 *Mar 29, 2002Oct 24, 2002Alorica Inc.Method, system, and program for customer service and support managementUS20050273369 *Mar 29, 2005Dec 8, 2005Hitachi, Ltd.Recall support system, recall support method, and programs thereforUS20060161392 *Oct 14, 2005Jul 20, 2006Food Security Systems, Inc.Food product contamination event management system and methodUS20090144104 *Nov 30, 2007Jun 4, 2009Scott Kevin JohnsonSystem and Method of Selectively Notifying Consumers of Product Recalls* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8036914 *Feb 19, 2009Oct 11, 2011Mckesson Financial Holdings LimitedSystems and methods for supporting drug or product recallsUS8239269 *Sep 11, 2009Aug 7, 2012Nintendo Of America Inc.System and/or method for handling returns involving products tied to post-paid subscriptions/servicesUS8311869Nov 15, 2007Nov 13, 2012Noblis, Inc.Alert distribution and management system and interface componentsUS8489461 *Jul 3, 2012Jul 16, 2013Nintendo Of America Inc.System and/or method for handling returns involving products tied to post-paid subscriptions/servicesUS20130238471 *Mar 6, 2013Sep 12, 2013Nintendo Of America Inc.Systems and/or methods involving linked manufacturer serial numbers and unique identifiers applied to products* Cited by examinerClassifications U.S. Classification705/28, 705/34, 705/30International ClassificationG06Q10/00, G06Q30/00Cooperative ClassificationG06Q30/02, G06Q10/087, G06Q30/04, G06Q50/22, G06Q40/12, G06Q20/203European ClassificationG06Q30/02, G06Q50/22, G06Q20/203, G06Q40/10, G06Q30/04, G06Q10/087Legal EventsDateCodeEventDescriptionJul 3, 2008ASAssignmentOwner name: NOBLIS, INC., VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRADY, PATRICK CHARLES;FIDDLEMAN, RICHARD HARDY;PATT-CORNER, ROBERT IRWIN;REEL/FRAME:021231/0776;SIGNING DATES FROM 20080306 TO 20080627Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRADY, PATRICK CHARLES;FIDDLEMAN, RICHARD HARDY;PATT-CORNER, ROBERT IRWIN;SIGNING DATES FROM 20080306 TO 20080627;REEL/FRAME:021231/0776Owner name: NOBLIS, INC., VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRADY, PATRICK CHARLES;FIDDLEMAN, RICHARD HARDY;PATT-CORNER, ROBERT IRWIN;SIGNING DATES FROM 20080306 TO 20080627;REEL/FRAME:021231/0776RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services