Low error rate interface for untrained users based on a method and system for event tracking

• US 20080086489A1
• Filed: 10/05/2006
• Published: 04/10/2008
• Est. Priority Date: 10/05/2006
• Status: Abandoned Application

• Current Assignee: David Wilkes
• Original Assignee: David Wilkes
• Inventors: Wilkes, David
• Application Number:
  US11/543,236
• Publication Number:
  US 20080086489A1
• Time in Patent Office: Days
• US Class Current: 707/101
• CPC Class Codes: G06K 2007/10504 Data fields affixed to objects or articles
• CPC Class Codes: G06K 7/10297 arrangements for handling protocols designed for non-contact record carriers such as RFIDs NFCs, e.g. ISO/IEC 14443 and 18092 cryptographic protocols H04L9/00; network security protocols H04L63/00; real-time communication protocols in data switching networks H04L65/00; network protocols for data switching network services H04L67/00
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/0875 Itemisation or classification of parts, supplies or services, e.g. bill of materials
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders

Abstract

A method of event tracking in a production environment includes storing each of at least one production event identifier in association with a respective plurality of expected production events prior to production. During production, a production event identifier is received from a user interface associated with the production environment to signal occurrence of one of the expected production events. In response to the receiving, it is automatically determined which one of the expected production events has occurred based on previous receipt of the received production event identifier. Event occurrence data relating to the expected production event determined to have occurred is then stored.

Claims

1. A method of event tracking in a production environment, comprising:

prior to production, storing each of at least one production event identifier in association with a respective plurality of expected production events;

during production, receiving a production event identifier from a user interface associated with the production environment to signal occurrence of one of the expected production events;

in response to the receiving, automatically determining which one of the expected production events has occurred based on previous receipt of the received production event identifier; and

storing event occurrence data relating to the expected production event determined to have occurred.

2. The method of claim 1, wherein previous receipt of the received production event identifier is indicated by a system state at the time the received production event identifier is received from the user interface, and the storing event occurrence data changes the system state.

3. The method of claim 1, wherein the expected production events include raw material delivery and raw material issue.

4. The method of claim 3, wherein one or more of the at least one production event identifiers comprises a raw material identifier, receipt of which from the user interface signals occurrence of one of delivery and issue of raw material.

5. The method of claim 4, wherein the event occurrence data for storing that relates to raw material delivery or raw material issue includes a raw material quantity received from the user interface.

6. The method of claim 5, wherein a raw material identifier and a raw material quantity are received simultaneously from the user interface.

7. The method of claim 6, wherein:

should event occurrence data have previously been stored in association with a received raw material identifier, signaling occurrence of issue of raw material upon receipt of the raw material identifier; and

otherwise

signaling occurrence of delivery of raw material upon receipt of the raw material identifier.

8. The method of claim 3, wherein the expected production events include finished goods completion and finished goods shipping.

9. The method of claim 8, wherein one or more of the at least one production event identifier comprises a finished goods identifier, receipt of which signals occurrence of one of completion and shipping of finished goods.

10. The method of claim 9, wherein the event occurrence data for storing that relates to finished goods completion or finished goods shipping includes a finished goods quantity received from the user interface.

11. The method of claim 10, wherein a finished goods identifier and a finished goods quantity are received simultaneously.

12. The method of claim 11, wherein:

should event occurrence data have previously been stored in association with a finished goods identifier, signaling occurrence of completion of finished goods upon receipt of the finished goods identifier; and

otherwise

signaling occurrence of shipping of finished goods upon receipt of the finished goods identifier.

13. The method of claim 5, wherein the user interface is operable by a production worker by entering a raw material identifier and a raw material quantity.

14. The method of claim 13, wherein the entering a raw material identifier comprises:

scanning a tag affixed to a shipping unit of raw material with an optical scanner.

15. The method of claim 13, wherein the entering a raw material identifier comprises:

bringing a radio frequency transceiver into receiving proximity with a radio frequency identification tag on a shipping unit of raw material.

16. The method of claim 10, wherein the user interface is operable by a production worker by entering a finished goods identifier and a finished goods quantity.

17. The method of claim 16, wherein the entering a finished goods identifier comprises:

scanning a tag affixed to a shipping unit of finished goods with an optical scanner.

18. The method of claim 16, wherein the entering a finished goods identifier comprises:

bringing a radio frequency transceiver into receiving proximity with a radio frequency identification tag on a shipping unit of finished goods.

19. A method of event tracking, comprising:

storing each of at least one event identifier in association with a respective plurality of expected events;

receiving an event identifier from a user interface to signal occurrence of one of the expected events;

in response to the receiving, determining which one of the expected events has occurred based on previous receipt of the received event identifier; and

on the basis of the determining, storing event occurrence data.

20. The method of claim 19, wherein previous receipt of the received event identifier is indicated by a system state at the time the received event identifier is received from the user interface, and the storing event occurrence data changes the system state.

21. The method of claim 19, wherein expected events associated with an event identifier are in sequence and event occurrence data for storing relates to a first expected event in the sequence that has not previously occurred.

22. The method of claim 19, further comprising:

receiving, with an event identifier, event parameter data from the user interface;

wherein the event occurrence data for storing includes the event parameter data.

23. The method of claim 22, wherein the determining comprises:

determining whether event occurrence data is already stored in association with a received event identifier.

24. The method of claim 19, wherein the expected events include production events.

25. The method of claim 19, wherein the expected events include medication delivery data.

26. The method of claim 25, wherein the medication delivery data includes patient identifiers, doses, dose intervals and medical carrier bin identifiers.

27. The method of claim 26, wherein each event identifier comprises a medical carrier bin identifier identifying a medical carrier bin, receipt of which signals occurrence of one of filling of the medical carrier bin with medication and delivery of medication from the medical carrier bin.

28. The method of claim 27, wherein:

should event occurrence data have previously been stored in association with a medical carrier bin identifier, the received event identifier signals occurrence of delivery of medication from the medical carrier bin identified by the received medical carrier bin identifier; and

otherwise

signals occurrence of filling with medication the medical carrier bin identified by the medical carrier bin identifier upon receipt of the medical carrier bin identifier.

29. The method of claim 27, wherein the user interface is operable by a medical worker by entering a medical carrier bin identifier.

30. The method of claim 29, wherein the entering a medical carrier bin identifier comprises:

scanning a tag affixed to a medical carrier bin with an optical scanner.

31. The method of claim 29, wherein the entering a medical carrier bin identifier comprises:

bringing a radio frequency transceiver into receiving proximity with a radio frequency identification tag on the medical carrier bin.

32. The method of claim 19, wherein the expected events include sporting match data.

33. The method of claim 32, wherein the sporting match data includes player data, team data, and one or more match schedules.

34. The method of claim 33, wherein each event identifier comprises a respective player identifier, receipt of which signals occurrence of a goal during a match by the player associated with the respective player identifier.

35. The method of claim 34, wherein the user interface is operable by a scorekeeper by entering a player identifier.

36. The method of claim 35, wherein the entering a player identifier comprises:

scanning a tag affixed to a player with an optical scanner.

37. The method of claim 35, wherein the entering a player identifier comprises:

bringing a radio frequency transceiver into receiving proximity with a radio frequency identification tag on the player.

38. The method of claim 19, wherein the storing each of at least one event identifier in association with a respective plurality of expected events comprises storing each of two event identifiers in association with a respective plurality of expected events.

39. The method of claim 38, further comprising:

preparing a report based on event occurrence data stored in association with a first of the two event identifiers and event occurrence data stored in association with a second of the two event identifiers; and

displaying the report.

40. The method of claim 39, wherein the preparing comprises:

comparing event occurrence data stored in association with the first of the two event identifiers and event occurrence data stored in association with the second of the two event identifiers with a predetermined usage standard to compute a raw material usage variance.

41. The method of claim 40, wherein the stored event occurrence data includes date/time data and the comparing is conducted in respect of event occurrence data stored during a pre-selected date/time period.

42. The method of claim 39, wherein the preparing comprises:

comparing event occurrence data stored in association with the first of the two event identifiers and event occurrence data stored in association with the second of the two event identifiers with predetermined price and cost standards to compute a gross margin.

43. The method of claim 42, wherein the stored event occurrence data includes date/time data and the comparing is conducted in respect of event occurrence data stored during a pre-selected date/time period.

44. A system for event tracking in a production environment, comprising:

a storage device;

a first user interface storing in the storage device each of at least one production event identifier in association with a respective plurality of expected production events;

a second user interface associated with the production environment receiving a production event identifier to signal occurrence of one of the expected production events during production; and

a processor, in response to the receiving, automatically determining which one of the expected production events has occurred based on previous receipt of the received production event identifier and storing in the storage device, event occurrence data relating to the expected production event determined to have occurred in the production environment.

45. The system of claim 44, wherein previous receipt of the received production event identifier is indicated by a system state at the time the received production event identifier is received from the second user interface, and the storing the event occurrence data changes the system state.

46. The system of claim 44, wherein the expected production events include raw material delivery and raw material issue.

47. The system of claim 46, wherein one or more of the at least one production event identifiers comprises a raw material identifier, receipt of which from the second user interface signals occurrence of one of delivery and issue of raw material.

48. The system of claim 47, wherein event occurrence data for storing that relates to raw material delivery or raw material issue includes a raw material quantity received from the second user interface.

49. The system of claim 48, wherein a raw material identifier and a raw material quantity are received simultaneously from the second user interface.

50. The system of claim 49, wherein the processor:

deems receipt of a raw material identifier to signal occurrence of issue of raw material should event occurrence data have previously been stored in the storage device in association with the received raw material identifier; and

otherwise

deems receipt of a raw material identifier to signal occurrence of delivery of raw material.

51. The system of claim 46, wherein the expected production events include finished goods completion and finished goods shipping.

52. The system of claim 51, wherein one or more of the at least one production event identifier comprises a finished goods identifier, receipt of which from the second user interface signals occurrence of one of completion and shipping of finished goods.

53. The system of claim 52, wherein the event occurrence data for storing that relates to finished goods completion or finished goods shipping includes a finished goods quantity received from the user interface.

54. The system of claim 53, wherein a finished goods identifier and a finished goods quantity are received simultaneously from the second user interface.

55. The system of claim 54, wherein the processor:

deems receipt of a finished goods identifier to signal occurrence of completion of finished goods should event occurrence data have previously been stored in association with the received finished goods identifier; and

otherwise

deems receipt of a finished goods identifier to signal occurrence of shipping of finished goods.

56. The system of claim 53, wherein the second user interface is operable by a production worker by entering a raw material identifier and a raw material quantity.

57. The system of claim 56, wherein a tag affixed to a shipping unit of raw material incorporates a raw material identifier and is capable of being optically scanned by a scanner associated with the second user interface.

58. The system of claim 56, wherein a radio frequency identification tag affixed to a shipping unit of raw material is capable of transmitting a raw material identifier to a radio frequency transceiver associated with the second user interface.

59. The system of claim 53, wherein the second user interface is operable by a production worker by entering a finished goods identifier and a finished goods quantity.

60. The system of claim 59, wherein a tag affixed to a shipping unit of finished goods incorporates a finished goods identifier and is capable of being optically scanned by a scanner associated with the second user interface.

61. The system of claim 59, wherein a radio frequency identification tag affixed to a shipping unit of finished goods is capable of transmitting a finished goods identifier to a radio frequency transceiver associated with the second user interface.

62. A system for event tracking, comprising:

a storage device;

a first user interface storing each of at least one event identifier in association with a respective plurality of expected events;

a second user interface receiving an event identifier to signal occurrence of one of the expected events; and

a processor, in response to the receiving, determining which one of the expected events has occurred based on previous receipt of the received event identifier and storing in the storage device event occurrence data on the basis of the determining.

63. The system of claim 62, wherein previous receipt of the received event identifier is indicated by a system state at the time the received event identifier is received from the second user interface, and the storing the event occurrence data changes the system state.

64. The system of claim 62, wherein expected events associated with an event identifier are in a respective sequence and event occurrence data for storing in the storage device relates to a first expected event in the respective sequence that has not previously occurred.

65. The system of claim 62, wherein the second user interface is configured to receive, with an event identifier, event parameter data;

wherein the event occurrence data for storing in the storage device includes the event parameter data.

66. The system of claim 65, wherein during the determining the processor determines whether event occurrence data is already stored in the storage device in association with a received event identifier.

67. The system of claim 62, wherein the expected events include production events.

68. The system of claim 62, wherein the expected events include medication delivery data.

69. The system of claim 68, wherein the medication delivery data includes patient identifiers, doses, dose intervals and medical carrier bin identifiers.

70. The system of claim 69, wherein each event identifier comprises a medical carrier bin identifier identifying a medical carrier bin, receipt of which by the second user interface signals occurrence of one of filling of the medical carrier bin with medication and delivery of medication from the medical carrier bin.

71. The system of claim 70, wherein the processor:

deems receipt of a medical carrier bin identifier to signal occurrence of delivery of medication from the medical carrier bin identified by the received medical carrier bin identifier should event occurrence data have previously been stored in the storage device in association with the received medical carrier bin identifier; and

otherwise

deems receipt of a medical carrier bin identifier to signal occurrence of filling with medication the medical carrier bin identified by the received medical carrier bin identifier.

72. The system of claim 70, wherein the second user interface is operable by a medical worker by entering a medical carrier bin identifier.

73. The system of claim 72, wherein a tag affixed to a medical carrier bin incorporates a medical carrier bin identifier and is capable of being optically scanned by a scanner associated with the second user interface.

74. The system of claim 72, wherein a radio frequency identification tag affixed to a medical carrier bin is capable of transmitting a medical carrier bin identifier to a radio frequency transceiver associated with the second user interface.

75. The system of claim 62, wherein the expected events include sporting match data.

76. The system of claim 75, wherein the sporting match data includes player data, team data, and one or more match schedules.

77. The system of claim 76, wherein each event identifier comprises a respective player identifier, receipt of which from the second user interface signals occurrence of a goal during a match by the player associated with the player identifier.

78. The system of claim 77, wherein the second user interface is operable by a scorekeeper by entering a player identifier.

79. The system of claim 78, wherein a tag affixed to a player incorporates a player identifier and is capable of being optically scanned by a scanner associated with the second user interface.

80. The system of claim 78, wherein a radio frequency identification tag affixed to a player is capable of transmitting a player identifier to a radio frequency transceiver associated with the second user interface.

81. A computer readable medium including a computer program for event tracking in a production environment, the computer program comprising:

computer program code storing each of at least one production event identifier in association with a respective plurality of expected production events prior to production;

computer program code receiving a production event identifier from a user interface associated with the production environment during production to signal occurrence of one of the expected production events;

computer program code automatically determining, in response to the receiving, which one of the expected production events has occurred based on previous receipt of the received production event identifier; and

computer program code storing event occurrence data relating to the expected production event determined to have occurred.

82. A computer readable medium including a computer program for event tracking, the computer program comprising:

computer program code storing each of at least one event identifier in association with a respective plurality of expected events;

computer program code receiving an event identifier from a user interface to signal occurrence of one of the expected events;

computer program code determining, in response to the receiving, which one of the expected events has occurred based on previous receipt of the received event identifier;

computer program code storing event occurrence data on the basis of the determining.

83. A method of event tracking, comprising:

storing each of at least one event identifier in association with a respective plurality of expected events;

receiving an event identifier from a user interface to signal occurrence of one of the expected events;

in response to the receiving, automatically determining which one of the expected events has occurred based on a system state at the time the received event identifier is received from the user interface; and

on the basis of the determining, adjusting the system state.