EP4022542A1 - Verfolgung von objekten - Google Patents
Verfolgung von objektenInfo
- Publication number
- EP4022542A1 EP4022542A1 EP20757612.5A EP20757612A EP4022542A1 EP 4022542 A1 EP4022542 A1 EP 4022542A1 EP 20757612 A EP20757612 A EP 20757612A EP 4022542 A1 EP4022542 A1 EP 4022542A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- event
- objects
- occurred
- last
- events
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/083—Shipping
- G06Q10/0833—Tracking
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Definitions
- the present invention is concerned with tracking objects.
- the present invention relates to a method, a device and a computer program product for tracking objects.
- Tracking objects plays an important role in many areas of the economy.
- One example is the tracking of goods along their value chain.
- Goods are usually given a unique identifier (e.g. a serial number) (serialization) so that they can be clearly identified at a later point in time.
- the unique identifier is usually printed as an optoelectronically readable code (barcode, 2D code) on the packaging of goods or is stored in an RFID transponder that is connected to the goods.
- the unique identifiers are recorded at various points in the value chain, e.g. during packaging, loading, upon arrival e.g. in a warehouse and / or upon receipt by a customer and / or the like, and the respective status changes of the goods are stored in a database.
- the status changes are usually recorded in a relational database in the form of a table.
- the table usually includes the unique identifiers of the goods as well as information on which (defined) events have occurred for the respective goods. This is shown by way of example in FIG. 1.
- 1 (a) shows five objects O1, 02, 03, 04 and 05. Each object can be identified using a unique identifier; in the present case based on the object identifiers 01, 02, 03, 04 and 05.
- Information on the objects is stored in table form in a data memory DB.
- the respective object is represented in the data memory by its object identifier.
- two events E1 and E2 are shown schematically.
- the event El has occurred for objects 01 and 02; event E2 occurred for objects 03, 04 and 05.
- the data memory DB is stored for the objects which event has occurred in each case.
- the event is represented in the table by an event identifier (El, E2).
- Fig. 1 (c) it is shown that two further events E3 and E4 have occurred.
- Event E3 occurred for objects 01 and 02;
- Event E4 has occurred for objects 03 and 04.
- the data memory DB it is in turn stored for the objects which event has occurred in each case.
- Fig. 1 (d) it is shown that four further events E5, E6, E7 and E8 have occurred.
- event E8 has occurred for object 05.
- the data memory DB in turn, it is stored for the objects which event has occurred in each case.
- the number N of objects that are tracked is significantly greater than the number n of events that occur.
- the number N of tracked Objects take on very great values. This means that a large amount of data has to be generated and stored.
- the data is used by various parties involved in the value chain of goods and must accordingly be transmitted from one party to another. This generates a large amount of data traffic.
- the task was to reduce the amount of data required for tracking objects.
- a first object of the present invention is therefore a method for tracking objects, comprising the steps:
- each object being represented by a unique object identifier in the first table, with the event that is stored for each object in the first table for each object respective object occurred last, with the respective previous event being entered in the second table for each event immediately preceding an event.
- Another object of the present invention is a device comprising
- control and computing unit is configured to cause the input unit to receive object identifiers of a plurality of objects, wherein the control and computing unit is configured to generate a first table, each object in the first table by the respective one Object identifier is represented, wherein the control and processing unit is configured to cause the input unit to receive information about events and about those objects for which the respective events have occurred, wherein the control and processing unit is configured in the first table to record for the objects which event occurred last, wherein the control and processing unit is configured to generate a second table and to record the immediately preceding event in the second table for each event which has been preceded by an event, the control and processing unit being configured to record the first table and the second Save the table in the data store.
- Another object of the present invention is a computer program product comprising a program code which is stored on a data carrier and which causes a computer system to carry out the following steps when the program code is loaded into the main memory of the computer system:
- the present invention is for tracking objects.
- An "object” is preferably a physical (tangible, corporeal) object.
- the objects described here are preferably goods.
- the term “goods” is understood to mean movable objects, which are or can be the subject of trade.
- Particularly preferred objects (goods) are pharmaceutical products (drugs, medicaments, diagnostics and others), pesticides (e.g. herbicides, insecticides, fungicides), pesticides (e.g. pesticides) and / or seeds.
- pesticides e.g. herbicides, insecticides, fungicides
- pesticides e.g. pesticides
- / or seeds e.g. pesticides
- it is also conceivable to apply the invention to disembodied objects such as data (music files, image files, video files, document files, presentation files, data packages, software modules, programming libraries or the like).
- An object within the meaning of the invention can comprise several components; for example, an object can be a product in a package. It is also conceivable that an object is a pallet or a transport box or a container or the like that comprises a plurality of objects (e.g. goods).
- the starting point for the present invention is a large number of objects.
- the term “multiplicity” means a number N of more than ten, preferably more than one hundred.
- the number N of objects that are tracked according to the invention is usually more than a thousand. As already described in the introduction, N is an integer.
- the plurality of objects includes both physical and incorporeal objects; For example, several objects can be combined into one logical object (see WO2018019720A1 page 5 line 27 to page 6 line 5).
- unique identifier indicates that the unique identifier can be assigned to exactly one object; there are no two objects that have the same identifier.
- the unique identifier can be a number or an alphanumeric code or a binary code or a hexadecimal code or the like.
- the respective object is processed under the unique identifier in a system for electronic data processing (EDP system), i.e. a unique identifier represents the respective object in the EDP system.
- EDP system electronic data processing
- the unique identifier of an object is also referred to in this description as the object identifier.
- Physical objects are usually equipped with an information carrier that includes the respective object identifier.
- the object identifier is printed as an optoelectronic code (e.g. as a barcode or 2D code (e.g. DataMatrix or QR code)) or that the object identifier is in an RFID transponder that is connected to the object is stored.
- the objects of the present invention are processed, ie they are subject to at least one process step, usually a plurality of process steps.
- a process step is also referred to as an event in this description.
- Such an event usually leads to a changed state / status of the respective object. Examples of events are: packing, loading, transporting, sending, receiving, unloading, reloading, repacking, unpacking, heating, cooling and the like. Events within the meaning of the invention can also be changes in status / changes in status which are undesirable, such as, for example, being lost, dropped, broken and the like.
- an object does not experience a change of state due to an event; For example, it is conceivable that several objects are combined into one logical object according to an event (collective formation). It is also conceivable that several events are combined in one event, for example an event can be combined with the
- transport includes the events “packing”, “loading”, “moving from a location A to a location B” and “unloading”.
- events can be defined by further information, e.g. when the event occurred, where the event occurred, by whom the event was initiated / carried out, why the event occurred and the like.
- An event (like an object) usually has a unique identifier by which the event can be identified.
- Such an event identifier represents the respective event in an IT system.
- the event identifier can be a number or an alphanumeric code or a binary code or a hexadecimal code or the like.
- the multiple events usually follow one another in time. If two events occur at the same time, they can either be combined into one event, or one can choose one of the events that is assumed to have occurred before the other event.
- an event history (chain of events) can be constructed in any case.
- An event history is a chain of chronologically consecutive events. In such an event history there is an event that last occurred for the respective object. This event is also referred to in this description as the “last event” or “latest event”. Furthermore, there is a first event in such an event history.
- each event in the event history is preceded by exactly one event (or, as described above, an event history can be constructed in which, with the exception of the first event, each event is preceded by exactly one event).
- This immediately preceding or preceding event is also referred to in this description as the previous event.
- the term “immediately” means that, according to the event history, no further event occurred (or was recorded) for the respective object between an event and its previous event.
- the number n of events that can occur for the large number of objects is usually smaller than the number of objects (n ⁇ N). Typically, specific events occur for multiple objects.
- An event Ei usually affects more than one object, an event E 2 more than one object, and so on.
- tracking means that the event history is recorded and recorded for the individual objects, so that the event history can be determined (reproduced) on the basis of the information recorded for each object.
- the event histories of objects are recorded and recorded with the aid of two tables, a first table and a second table.
- the term “table” is to be interpreted broadly.
- the term “table” is understood to mean any orderly compilation of data.
- a first table contains information about the objects that are being tracked.
- the last event (only) is entered for each object for which at least one event has occurred.
- the immediately preceding event (the preceding event) is entered for each event that has occurred for at least one object and which has been preceded by at least one event.
- a new event E occurs for a number N of objects
- the last events already entered in the first table for the objects are replaced by the new (last) event E.
- the new event E is entered in the second table and for the new event E it is entered which event immediately preceded event E.
- the last event for this object is first identified in the first table. You then use the second table to check whether an event preceded the last event. If not, the event history only consists of the last event. If a previous event is listed for the last event in the second table, the event history includes at least the last event and its previous event. The second table is now used to check whether the previous event itself has a previous event. If not, the chain of events only consists of the last event and its previous event. If, on the other hand, the preceding event of the last event has a preceding event, the chain of events includes at least the last event, its preceding event and the preceding event of the preceding event. The process of checking whether there is another previous event continues until there is no further previous event. The event history then consists of the last event and all identified previous events.
- FIG. 1 schematically shows the tracking of objects according to the previous (classic) procedure.
- Figures 1 (a) to 1 (d) have already been described in detail above.
- FIG. 2 shows schematically and by way of example a preferred embodiment of the present invention.
- the situation shown in FIG. 2 (a) follows in time the situation shown in FIG. 1 (a).
- the starting point of the invention are the five objects O1, 02, 03, 04 and 05 already shown in FIG. 1 (a), which can be identified by their unique identifiers.
- a data memory DB information on the objects is collected in table form on the basis of the unique object identifiers.
- two events E1 and E2 have occurred. Event El affects objects 01 and 02; Event E2 relates to objects 03, 04 and 05.
- a first table (Tab.
- FIG. 2 (b) (as in FIG. 1 (c)) two new events have occurred, E3 and E4, with event E3 relating to objects O1 and 02 and event E4 relating to objects 03 and 04.
- event E3 relating to objects O1 and 02
- event E4 relating to objects 03 and 04.
- the first table (Tab. 1) (E3 for 01 and 02; E4 for 03 and 04 and E2 for 05).
- the second table (Tab. 2) the corresponding previous event is recorded for each event that has a previous event (El is the previous event of E3 and E2 is the previous event of E4; El and E2 in turn have no previous events).
- the history of the events that have taken place can be read off for each object. This is explained using the example of object 01.
- the last event that occurred for object 01 is event E3.
- the event E3 preceded the event E3.
- the event E1 is not listed in the second table (or, as described in relation to FIG. 2 (a), it is recorded in the second table for the event E1 that it has no preceding event). Accordingly, the event history for object 01 is: E1 ⁇ E3.
- the procedure for tracking objects shown in FIG. 2 (b) manages with fewer entries in the data memory than the procedure shown in FIG. 1 (c); in the case of Fig. 2 (b) there are 7 entries (distributed over two tables) and in the case of Fig. 1 (c) there are 9 entries.
- Fig. 2 (c) (as in Fig. 1 (d)) four new events have occurred, E5, E6, E7 and E8, with the event E5 the objects 01 and 02, the event E6 the object 03, the event E7 relates to object 04 and event E8 relates to object 05.
- first table (Tab. 1), in turn, only the event that occurred last is recorded for each object. This means that the “new, most recently occurred event” replaces the “previously last occurred event”.
- the second table (Tab. 2), the respective previous event is recorded for each event that had a previous event.
- the history of the events that have taken place can be read off for each object. This is explained using the example of object 04.
- the last event that occurred for object 04 is event E7.
- event E4 preceded event E7.
- event E2 preceded event E4.
- the event E2 is not listed in the second table (or, as described with reference to FIG. 2 (a), it is recorded in the second table for the event E2 that E2 has no preceding event). Accordingly, the event history for object 04 is: E2 ⁇ E4 ⁇ E7.
- the procedure for tracking objects shown in FIG. 2 (c) manages with fewer entries than the procedure shown in FIG. 1 (d); in the case of Fig. 2 (c) there are 11 entries (distributed over two tables) and in the case of Fig. 1 (d) there are 14 entries.
- the difference in the number of entries is comparatively small (11 entries compared to 14 entries in relation to the scenarios in FIGS. 2 (c) and 1 (d)).
- the events listed in this example only affected a small number of objects.
- events E6, E7, and E8 each only affected a single object.
- the numbers of the entries for the procedure shown in FIGS. 1 (classic) and 2 (according to the invention) are the same large.
- events affect a large number of objects.
- the tracking of objects according to the invention requires far fewer entries in a data memory than the classic procedure.
- FIG. 3 shows, by way of example and schematically, a further embodiment of the present invention.
- the event history is shown schematically for five objects O1, 02, 03, 04 and 05.
- the event histories are for objects 01 and 02: E1 ⁇ E3 for objects 03 and 04: E2 ⁇ E4 for object 05: E2.
- the scenario shown in FIG. 3 (a) corresponds to the scenario shown in FIG. 2 (b).
- the scenario shown in FIG. 3 (b) follows on in time from the scenario shown in FIG. 3 (a).
- a new event E6 has occurred.
- the event E6 concerns the objects 02, 03, 04 and 05. If, as previously described, one would now replace the last event in the first table (Tab. 1) with the event E6 for each object affected by the event E6, and in the second table (Tab. 2) record its predecessor event for event E6, there would be three predecessor events for event E6, depending on which object one would assume.
- the combination of the first table and the second table would also no longer allow the event history to be reproduced for each object.
- the reason for this discrepancy is that the same event occurred for objects 02, 03, 04 and 05, but the objects have a different event history. Something like this can happen, for example, if the events are defined very generically, such as the event "Receipt by the customer”. To avoid this discrepancy, events can be defined more specifically to prevent an event from occurring in different places from different event histories.
- a preferred embodiment generates different event identifiers for an event that occurs for objects that have different event histories. This is shown schematically and by way of example in FIG. 3 (c).
- the information is received that an event E6 has occurred which affects objects 02, 03, 04 and 05.
- the first table (Tab. 1) is used to check whether all objects that are affected by event E6 have the same last event.
- the last events are from Fig. 3 (a) in the first table from Fig. 3 (c).
- Objects 03 and 04 have the same last event: E4.
- Objects 02 and 05 however, have other last events: E3 (in the case of 02) and E2 (in the case of 05).
- the first step is to form groups. As many groups are formed as there are different last events for the objects concerned. In the present case, there are three different last events for the affected objects 02, 03, 04 and 05: E3, E4 and E2. So three groups are formed. The last events are assigned to the groups; that is, there is a group to which the last event E3 is assigned, there is a group to which the last event E4 is assigned, and there is a group to which the last event E2 is assigned. The objects are assigned to the groups.
- Each object is assigned to exactly one group, namely the group to which the event is assigned, which is the last event for the respective object.
- Object 02 is assigned to the group to which the last event E3 is assigned.
- Objects 03 and 04 are assigned to the group to which event E4 is assigned.
- the object 05 is assigned to the group to which the last event E2 is assigned.
- just as many event IDs are generated for the new event E6 as there are groups; in the present case three event identifiers, namely the event identifiers E6a, E6b and E6c.
- Each event ID is assigned to exactly one group; this can be done arbitrarily;
- the group with the object 02 is assigned the event ID E6a
- the group with the objects 03 and 04 is assigned the event ID E6b
- the group with the object 05 is assigned the event ID E6c.
- the last event from FIG. 3 (a) in the first table for each object is replaced by that event identifier which is assigned to the group to which the respective object belongs.
- the last event for object 02 is event E6a
- the last event for objects 03 and 04 is event E6b
- the last event for object 05 is event E6c.
- the previous last event is E3. According to FIG.
- a new entry is created for each of the last events that occurred in the first table. For the last event E5 it is recorded that the previous event is the event E3; for the last event E6a it is recorded that the previous event is the event E3; for the last event E6b it is recorded that the previous event is the event E4; for the last event E6c it is recorded that the previous event is the event E2.
- Fig. 4 shows schematically and by way of example an embodiment of the device according to the invention.
- the device (10) comprises an input unit (20), a control and computing unit (30), a data memory (40) and an output unit (50).
- the device (10) receives information about events and the objects that are affected by the events via the input unit (20).
- the control and computing unit (30) is configured to manage the information on the events and the objects in order to be able to reproduce an event history for each object. For this purpose, the control and computing unit (30) generates and maintains two tables, a first table and a second table.
- the tables can be stored in the data memory (40) and / or displayed to a person via the output unit (50).
- the data memory (40) can be an integral part of the device (10); but it is also conceivable that the data memory (40) is a separate unit is executed, which the control and computing unit (30) can access, for example via a network.
- the device according to the invention can, for example, be designed as a computer system.
- a "computer system” is a system for electronic data processing that processes data using programmable arithmetic rules. Such a system usually comprises a “computer”, that unit which comprises a processor for performing logical operations, and peripherals.
- peripherals are all devices that are connected to the computer and are used to control the computer and / or as input and output devices. Examples of this are monitors (screens), printers, scanners, mice, keyboards, drives, cameras, microphones, loudspeakers, etc. Internal connections and expansion cards are also considered peripherals in computer technology.
- Today's computer systems are often divided into desktop PCs, portable PCs, laptops, notebooks, netbooks and tablet PCs and so-called handheids (e.g. smartphones); all of these devices can be used to practice the invention.
- the inputs into the computer are made via input means such as a keyboard, a mouse, a microphone, a network connection, an external data memory and / or the like.
- input means such as a keyboard, a mouse, a microphone, a network connection, an external data memory and / or the like.
- the selection of an entry from a virtual menu or a virtual list or the clicking of a selection box and the like should also be understood as input.
- Outputs usually take place via a screen (monitor), on a printer, via loudspeakers and / or by storage on a data memory.
- FIG. 5 shows schematically in a flowchart those steps which a computer system carries out in a preferred embodiment of the present invention when the computer system according to the invention is loaded in a main memory of the computer system and is being carried out.
- the computer system receives information on an event E and on one or more objects O that are affected by the event. It usually receives the event ID of the event that has occurred and a list of object IDs of those objects that are affected by the event.
- a further step (110) it is checked whether the event only affects a single object (
- 1?).
- the updated tables (Tab. 1 and / or Tab. 2) are saved in a further step (150) in a data memory (DB: Tab. 1, Tab. 2).
- a further step (170) checks whether they all have the same last event (same LE?).
- steps (140) and (150) are carried out for each individual object, that is, in the second table (Tab. 2) it is recorded that the last event is the previous event of event E, and in the first table (Tab. 1) it is recorded that event E is the last event for the respective object.
- the updated tables (Table 1 and Table 2) are then stored in the data memory (step (150)).
- step (170): “n” groups are formed in a further step (180) and the objects are assigned to the groups on the basis of the last events (“grouping”). If two objects have the same last event, they are assigned to the same group. There are as many groups as there are different final events.
- new event IDs are generated for event E (“event ID creation”). As many event IDs are generated as there are groups.
- event ID creation As many event IDs are generated as there are groups.
- the generated event IDs are assigned to the groups (“assignment”); this can be done arbitrarily; an event identifier is assigned to each group. As a result of the group membership, an event identifier is also assigned to each object.
- the first table (Tab. 1) is used to check for the individual objects which last event is recorded for them in the first table (“which LE?”).
- the respective last event is the previous event for the generated event identifier that is assigned to the object.
- the corresponding preceding event is recorded in the second table for each generated event identifier.
- the previous last event is replaced by the generated event identifier assigned to the object.
- the updated tables (Table 1 and Table 2) are stored in the data memory
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Human Resources & Organizations (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Development Economics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP19194253.1A EP3786866A1 (de) | 2019-08-29 | 2019-08-29 | Verfolgung von objekten |
| PCT/EP2020/073588 WO2021037775A1 (de) | 2019-08-29 | 2020-08-24 | Verfolgung von objekten |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| EP4022542A1 true EP4022542A1 (de) | 2022-07-06 |
Family
ID=67810389
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP19194253.1A Withdrawn EP3786866A1 (de) | 2019-08-29 | 2019-08-29 | Verfolgung von objekten |
| EP20757612.5A Withdrawn EP4022542A1 (de) | 2019-08-29 | 2020-08-24 | Verfolgung von objekten |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP19194253.1A Withdrawn EP3786866A1 (de) | 2019-08-29 | 2019-08-29 | Verfolgung von objekten |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US20220277262A1 (de) |
| EP (2) | EP3786866A1 (de) |
| WO (1) | WO2021037775A1 (de) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8010887B2 (en) * | 2001-09-21 | 2011-08-30 | International Business Machines Corporation | Implementing versioning support for data using a two-table approach that maximizes database efficiency |
| US7621447B1 (en) * | 2003-01-31 | 2009-11-24 | Massachusetts Institute Of Technology | Method and apparatus for routing data in an automatic identification system |
| US20100127871A1 (en) * | 2008-11-26 | 2010-05-27 | Pontin Srl | System and method for verification of shipped products using rfid tags |
| US8782023B1 (en) * | 2012-01-26 | 2014-07-15 | Google Inc. | Versioned database cache |
| JP2019532442A (ja) | 2016-07-26 | 2019-11-07 | バイエル、ビジネス、サービシズ、ゲゼルシャフト、ミット、ベシュレンクテル、ハフツングBayer Business Services Gmbh | 階層データの同期 |
-
2019
- 2019-08-29 EP EP19194253.1A patent/EP3786866A1/de not_active Withdrawn
-
2020
- 2020-08-24 WO PCT/EP2020/073588 patent/WO2021037775A1/de not_active Ceased
- 2020-08-24 US US17/638,786 patent/US20220277262A1/en not_active Abandoned
- 2020-08-24 EP EP20757612.5A patent/EP4022542A1/de not_active Withdrawn
Also Published As
| Publication number | Publication date |
|---|---|
| EP3786866A1 (de) | 2021-03-03 |
| US20220277262A1 (en) | 2022-09-01 |
| WO2021037775A1 (de) | 2021-03-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1237098B1 (de) | Integriertes Datenbank-Verbund-System | |
| DE68924525T2 (de) | Gemeinschaftsobjektszustandsanzeige. | |
| EP3491543A1 (de) | Synchronisation hierarchischer daten | |
| DE102012001406A1 (de) | Automatische Konfiguration eines Produktdatenmanagementsystems | |
| EP3901713A1 (de) | Verfahren und system zum betrieb einer technischen anlage mit einem optimalen modell | |
| DE202014005278U1 (de) | Einbetten von archivierten Daten in eine Datenquelle | |
| EP4022542A1 (de) | Verfolgung von objekten | |
| DE102014207874A1 (de) | Verfahren zur automatisierten Erstellung eines eine technische Zeichnung charakterisierenden Datensatzes | |
| EP2014810B1 (de) | Verfahren zur Herstellung von Warenlaufkarten | |
| DE10325843B4 (de) | Verfahren, Drucksystem, Computer und Computerprogramm zum Verwalten von Resourcen zur Verwendung in einem resourcenbasierten Dokumentendatenstrom | |
| DE102018128498A1 (de) | Verfahren zur Bauteilverfolgung | |
| DE112010003922T5 (de) | Verringern von Mehraufwänden bei einer Anwendungsverarbeitung | |
| DE19539477A1 (de) | Verfahren zur automatisierten optimalen Redundanz-Auslegung von Messungen für die Leittechnik in Kraftwerken | |
| DE102018006211B4 (de) | Verfahren zum Protokollieren von Erkennungsmerkmalen für Erzeugnisse | |
| EP1926019B1 (de) | Datenaustauschverfahren und Steuerverfahren zwischen Softwarebausteinen sowie wiederverwendbare Softwarebausteine | |
| EP4033211B1 (de) | Absicherung und dokumentation eines verarbeitungsprozesses von rohstoffen zur arzneimittelherstellung | |
| DE102010011664A1 (de) | View-Server und Verfahren zur Bereitstellung von spezifischen Daten von Objekten und/oder Objekttypen | |
| AT223849B (de) | Schaltungsanordnung zum Ermitteln der in einem Betrieb zu fertigenden Geräte oder Bauteile | |
| DE202022106662U1 (de) | Lagerlogistiksystem zum Waren- und Lagerplatzabgleich sowie entsprechende Verwendung | |
| EP1577806B1 (de) | Objektfilter zur Organisation der Verteilung von Postsendungen | |
| DE10064030A1 (de) | Verfahren und Vorrichtung zum Bearbeiten eines physikalischen Objekts, Computerprogramm-Element und Computerlesbares Speichermedium | |
| DE4338738A1 (de) | Elektronische Archivierungsverfahren von Unterlagen | |
| DE10211719A1 (de) | Verfahren und Vorrichtung zur Kommissionierung von Waren | |
| DE102008063658A1 (de) | Verfahren zum Steuern und/oder Überwachen mindestens eines Prozesses, insbesondere eines Materialflussprozesses | |
| EP4498286A1 (de) | Computer-implementiertes verfahren zum trainieren eines machine-learning-modells |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: UNKNOWN |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
| 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 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
| 17P | Request for examination filed |
Effective date: 20220329 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
| DAV | Request for validation of the european patent (deleted) | ||
| DAX | Request for extension of the european patent (deleted) | ||
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN |
|
| 18W | Application withdrawn |
Effective date: 20230905 |