EP2186017A1 - Procédé et système pour identifier des objets - Google Patents

Procédé et système pour identifier des objets

Info

Publication number
EP2186017A1
EP2186017A1 EP08787054A EP08787054A EP2186017A1 EP 2186017 A1 EP2186017 A1 EP 2186017A1 EP 08787054 A EP08787054 A EP 08787054A EP 08787054 A EP08787054 A EP 08787054A EP 2186017 A1 EP2186017 A1 EP 2186017A1
Authority
EP
European Patent Office
Prior art keywords
objects
classes
relations
standard
product
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
EP08787054A
Other languages
German (de)
English (en)
Inventor
Jan-Gregor Fischer
Jörg MANDEL
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.)
Fraunhofer Gesellschaft zur Forderung der Angewandten Forschung eV
Siemens AG
Original Assignee
Siemens AG
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 Siemens AG filed Critical Siemens AG
Publication of EP2186017A1 publication Critical patent/EP2186017A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06NCOMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N5/00Computing arrangements using knowledge-based models
    • G06N5/02Knowledge representation; Symbolic representation
    • G06N5/022Knowledge engineering; Knowledge acquisition
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/36Creation of semantic tools, e.g. ontology or thesauri
    • G06F16/367Ontology
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/067Enterprise or organisation modelling

Definitions

  • the invention relates to a method and system for the semantic description of objects in an integrated product model for the replacement of conventional numbering systems.
  • An object be it a material object, such as a vehicle to be manufactured or an immaterial object
  • Service product such as a financial service, can go through several process stages of an overall process.
  • Fig. 1 serves to illustrate the problem underlying the invention.
  • a product or object passes from a process stage N to a subsequent process stage N + 1.
  • the process stage N is a supplier who delivers a part to be assembled to a process stage N + 1 in another company in which an assembly of the delivered objects or vendor parts takes place.
  • the delivery part or object is, for example, a pump for a motor vehicle with a specific identification.
  • An object data transformation forms part of the product data management within a manufacturing company. Even within the same process stage, different nomenclatures are used in some cases. If, for example, a 3D production development takes place, different software tools of involved areas such as logistics or assembly planning as well as suppliers can have different nomenclatures.
  • phase model describes a different view of the product or article and uses different descriptors.
  • the phase model identifies and classifies products using a variety of numbering systems, and changes to identification, classification, or structuring in a phase model can directly impact other phase models.
  • Products or articles from external suppliers can be identified without further ado using the numbering system of the supplier company. From the point of view of the customer or the company assembling the individual parts, integration into the own numbering system is necessary. In a conventional system, this transformation between two numbering systems can be performed by corresponding manually generated transformation tables.
  • a transformation between a company-internal numbering system and external numbering systems as well as changes to the master and structural data in the supplier network represent a considerable constant adaptation effort for the company. There is also a constant risk of missing data integrity and a lack of consistency of the product data. Many companies even use different nomenclatures or numbering systems for different company divisions. For example, an item or a product is referred to differently in the development department than in production or in quality assurance. Therefore, conventional systems often require a transformation between nomenclatures of different divisions.
  • Fig. 2 shows a conventional hierarchically constructed system for the identification and classification of products or articles with so-called feature strips.
  • a class "pump” has two subclasses “piston pump” and “sinus pump”, which in turn contain subclasses.
  • the subclass "piston pump” for its part, the subclasses “piston pump steel” and the subclass “piston pump brass” on.
  • the conventional labeling of products shown in FIG. 2 is carried out, for example, according to a nomenclature of a supplier. If the supplier delivers pumps to a customer, for example a vehicle manufacturer, he is forced to translate or transform the parts lists into the delivery of the articles into his own nomenclature. If the supplier changes his nomenclature or adds other pumps to his range, the purchaser or vehicle manufacturer must supplement his nomenclature accordingly. As can be seen from the example shown in FIG. 2, FIG If, for example, a complex product involves a large number of installed articles or vendor parts, adapting or modifying the transformations between the various labeling systems represents a considerable expense for the company.
  • the situation is further exacerbated when a customer receives vendor parts from a large number of different suppliers, each with its own numbering system. If a customer wants to obtain corresponding delivery parts from another supplier who offers vendor parts at more favorable delivery conditions, the customer is also forced to first adapt his numbering system, whereby he must define transformations from the numbering system of the new supplier to his own numbering system. The effort involved makes it difficult for the customer to switch from a previous supplier to another supplier.
  • the invention provides a method for identifying objects which pass through different process stages, wherein the objects for the respective process stages are described ontologically and classes and / or relations for characterizing the objects are linked to one another as an equivalent.
  • the objects are described in the ontology description language OWL (Web Ontology Language).
  • a process stage consists of one or more sequential or parallel process phases, each of which has an associated nomenclature. In one embodiment of the method according to the invention, each process stage has its own name space or nomenclature.
  • an object is a tangible object or an immaterial service product.
  • a plurality of process stages form a process domain.
  • standard classes and standard relations are provided within a process domain.
  • standard classes and standard relations of a process stage within a process domain are automatically linked with corresponding standard classes and standard relations of another process stage of the process domain.
  • classes and / or relations of a process stage are automatically linked to one another by means of predetermined rules.
  • the rules used are automatically generated by learning methods.
  • the rules used are automatically instantiated on the basis of predefined templates for generating rules, so-called rule templates.
  • object identifiers are additionally assigned to the objects identified by linkage.
  • the invention further provides a system for identifying objects which pass through different process stages, wherein the objects for the respective process stages are described ontologically and classes and / or relations for characterizing the objects are linked as being equivalent to one another.
  • Fig. 2 is a conventional marking system according to the
  • Fig. 3 is a diagram illustrating the operation of the method according to the invention for the identification of
  • Fig. 6 shows an example of a relation as used in the method according to the invention
  • FIG. 7 shows an example of an instance for the example given in FIG. 4.
  • a system 1 according to the invention for marking objects has a plurality of process stages which pass through the objects.
  • objects sequentially go through several process stages 2-1 to 2-4 of a first domain before going through two process stages 2-5 to 2-6 of a second domain.
  • Several process stages form a so-called process domain.
  • the process stages are any process stages, for example, process stages of a manufacturing process or a financial process.
  • process stage 2-1 is a process stage for developing a complex object, such as a vehicle.
  • Stage 2-2 is formed by a factory preparation stage and stage 2-3 by a mounting stage for assembling the product.
  • the process stage 2-4 represents a stage for quality assurance of the vehicle.
  • the process stages 2 are linked in series with one another. In alternative embodiments, the process stages can also be linked together as desired.
  • the objects for the respective process stages 2 are described ontologically.
  • the objects are described ontologically using the Web Ontology Language (OWL).
  • OWL Web Ontology Language
  • Ontology is a knowledge base in which information about or about the object is stored by a network of relationships, such as classes, subclasses, relations, and attributes.
  • the ontology includes structured and organized concepts and assignments that describe a product in individual process stages of a product cycle. Products are instantiated in the ontological model at their manufacturing time. The connection of a real product with the representation of the product as an object in a modeled product class occurs through instantiation of the class.
  • 4 shows an example of an ontological description of objects in two process stages for explaining the method according to the invention. The example shown is a process stage of a pump supplier and an assembly company where pumps are installed in a complex product.
  • a class “Product” is defined with the properties or attributes “production time”, “height”, “length”, “weight” ( Weight) . Due to the relation “consisting of", a product can again consist of a single product or several products.
  • the Product class is a subclass of the pump class, with the properties or attributes of the Product class inherited from this Pump subclass.
  • the subclass “Pump” has in turn two subclasses “Piston Pump” and “Sinus Pump”, which also inherit the properties or attributes of the upper class “Product”.
  • the subclass “Piston Pump” has two subclasses "Piston Pump”
  • the supplier describes the products he produces. In the example given, the supplier produces pistons for a pump.
  • the class "Piston” (piston) has subclasses, namely "Piston Steel"
  • classes and / or relations of the ontological description are linked as equivalent to one another for the purpose of marking objects.
  • the class "Product” is defined as equivalent to the class of individuals produced by the class "Production Resource”.
  • a clear identification of an object is no longer carried out as in conventional methods on the basis of a given object ID or object name but on the basis of the semantic / ontological description of the object in different process stages which are linked to one another.
  • FIG. 5 shows an example of a mapping between two ontological product descriptions for the two process stages illustrated in FIG. 4.
  • the OWL description language is based on XML.
  • Two different namespaces XMLNS are defined for the two different process levels.
  • the class "Product" in the assembly process stage is defined as equivalent to the class of those individuals who are excluded from the class "Production Resource” in the pro supplier's supplier.
  • the ontologies of the various process stages which belong for example to different companies or company parts, are linked together. For the unambiguous identification of instances, meaningful relations or properties are selected which sufficiently restrict the result space of the identification process.
  • a product can be identified unambiguously by specifying the product class, the product variant, the place of production, ie an exact location of a production resource and a production date, and possibly by specifying the product structure.
  • a particular pump or instance of the "Piston Pump Steel” class can be uniquely individualized based on the inherited properties of the "Product” superclass and associated classes or relationships.
  • a specific piston pump manufactured from steel can be clearly individualized based on the inherited attributes or characteristics of the upper class "Product" and linked classes or relations. For example, a particular piston pump made of steel becomes a certain production time, a certain height, a certain length, and a certain weight
  • a piston pump steel made of steel will be on 10 May
  • a relation can link several classes together.
  • a relation can connect two classes as a binary relation or three classes as a ternary relation.
  • Fig. 5 shows as an example a ternary relation logically linking three classes together, namely the class "Product P", the class “Employee M” and the class "Tool W".
  • the relation may be for example: The product P is produced by the employee M using a tool W.
  • a binary relation links two classes together.
  • a property of a class can be considered as a non-essential relation, i. the relation only applies to this class.
  • a plurality of process stages form a so-called process domain, for example a plurality of process stages within a company.
  • a process domain can also include, for example, all process stages within an industry, for example within the automotive industry.
  • standard classes and standard relations can be defined or provided within a process domain. It can be a standard class or standard relation in a process stage of the process domain, in one possible embodiment, be automatically linked to a corresponding standard class or standard relation of another process stage of the same process domain.
  • FIG. 7 shows an example of an instantiation of the ontological description model shown in FIG. 4.
  • An entity or an individual who does not have to be provided with an object ID himself is clearly individualized by his interrelationships, in particular due to the inherited properties and the link with the manufacturing process of the supplier.
  • the instance or individual object is represented by an exact time of manufacture, namely 5 October 2007 at 14:53 hours and 30 seconds, with a length of 60 and a weight of 32, 8 and the relationship established by equivalence linkage with the ontological description of a steel piston ("Piston Steel 25cm") of the supplier 1 (SUPPL) incorporated therein.
  • Piston Steel 25cm steel piston
  • the individual pump is linked by linking the ontological descriptions of the two process stages and additionally specifying the instance or the individual Product clearly individualized.
  • the steel piston contained in the pump has a length of 25 cm.
  • the steel piston was manufactured by the supplier
  • the production of the steel piston was carried out by an instance of a production resource ("Production Resource") belonging to a factory (plant) of the supplier SUPPL in Bremen.
  • the production of the steel piston was carried out at an individual production time on 5 February 2007 at 4:31:59 clock, the steel piston has a length (length) of 25 cm and a weight (weight) of 13.4.
  • a particular piston pump steel produced is not provided with an object identification, for example an article code or a name, as in conventional methods, but is uniquely individualized by means of an ontological network of relationships which extends over a plurality of process stages.
  • object identification for example an article code or a name
  • a piston pump made of steel is individualized by an instance of an ontological relationship mesh, as shown by way of example in FIG.
  • the entity may additionally be given a designation which is easy to understand for a user, for example.
  • the instance or object uniquely identified by the ontological relationship mesh in FIG. 7 can additionally be given a name, such as "steel piston pump HANS”.
  • the identification of an object for example, a manufactured product, regardless of whether it has gone through the production, just in a warehouse is present as part of a bill of materials installed in a module of a third party company or appears in analyzes.
  • no numbering or name marking is required.
  • the individualization or marking of the objects takes place during the
  • the method according to the invention implicitly by its properties and relations.
  • no transformation of different nomenclatures is required.
  • the inventive method or the inventive system is characterized by high flexibility and unlimited expandability.
  • the method and system according to the invention can be integrated into a product management system. With the introduction of ontology-based models, traditional systems eliminate the need for numbering systems. It is possible to both parent and
  • the method and system according to the invention are suitable for any articles or products, i. for both physical products and service products.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Computational Linguistics (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Computing Systems (AREA)
  • Operations Research (AREA)
  • Mathematical Physics (AREA)
  • Development Economics (AREA)
  • Evolutionary Computation (AREA)
  • Educational Administration (AREA)
  • Artificial Intelligence (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Animal Behavior & Ethology (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Procédé et système pour identifier des objets qui passent par différentes étapes d'un processus. Les objets sont décrits de manière ontologique pour les étapes respectives du processus, et des catégories et/ou des relations destinées à identifier les objets sont liées entre elles en équivalence.
EP08787054A 2007-09-06 2008-08-08 Procédé et système pour identifier des objets Ceased EP2186017A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102007042442A DE102007042442A1 (de) 2007-09-06 2007-09-06 Verfahren und System zur Kennzeichnung von Objekten
PCT/EP2008/060462 WO2009033902A1 (fr) 2007-09-06 2008-08-08 Procédé et système pour identifier des objets

Publications (1)

Publication Number Publication Date
EP2186017A1 true EP2186017A1 (fr) 2010-05-19

Family

ID=39968243

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08787054A Ceased EP2186017A1 (fr) 2007-09-06 2008-08-08 Procédé et système pour identifier des objets

Country Status (4)

Country Link
US (1) US20100185553A1 (fr)
EP (1) EP2186017A1 (fr)
DE (1) DE102007042442A1 (fr)
WO (1) WO2009033902A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102009058901A1 (de) 2009-12-18 2010-07-29 Daimler Ag Computergestütztes Verfahren und Vorrichtung zur Montageaufwandsermittlung
US11946886B2 (en) 2014-12-01 2024-04-02 Wts Llc Fluid heating system
US10495720B2 (en) 2014-12-01 2019-12-03 Wts Llc Control valve assembly for a fluid heating system
US10168412B2 (en) 2014-12-01 2019-01-01 Wts Llc Dual axis tracking device
WO2018094330A1 (fr) 2016-11-18 2018-05-24 Wts Llc Système de chauffage de fluide numériqu
DE102016224457A1 (de) 2016-11-29 2018-05-30 Siemens Aktiengesellschaft Verfahren zur Prüfung, Vorrichtung und Computerprogrammprodukt
DE102018201726A1 (de) 2018-02-05 2019-07-11 AUDI HUNGARIA Zrt. Verfahren und System zum Analysieren eines Bauteilsatzes

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060074980A1 (en) * 2004-09-29 2006-04-06 Sarkar Pte. Ltd. System for semantically disambiguating text information
JP4848128B2 (ja) * 2004-12-24 2011-12-28 インターナショナル・ビジネス・マシーンズ・コーポレーション データベース・システム、データベース・システムのためのコンピュータ実行可能な方法、プログラムおよびデータベース・システムにおける索引テーブルをアップデートする方法

Non-Patent Citations (2)

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

Also Published As

Publication number Publication date
US20100185553A1 (en) 2010-07-22
DE102007042442A1 (de) 2009-03-12
WO2009033902A1 (fr) 2009-03-19

Similar Documents

Publication Publication Date Title
EP0855062B1 (fr) Systeme d'informations et procede de memorisation de donnees dans un systeme d'informations
WO2009033902A1 (fr) Procédé et système pour identifier des objets
DE69931004T2 (de) Verfahren und Vorrichtung zur Datenverarbeitung
EP1699005A1 (fr) Integration de MES et ingenierie de contrôle
EP3584751A1 (fr) Procédé de production d'un jumeau numérique
WO2004083983A2 (fr) Comparaison de modeles de systemes complexes
DE10244685A1 (de) Produktkonfigurationsverfahren und -system
EP1561180A2 (fr) Dispositif et procede de generation d'un outil de traitement
DE102010004192A1 (de) Verfahren zur Konstruktion industrieller Anlagen
DE10115046A1 (de) Verfahren und Einrichtung zur Erzeugung eines Abbildes eines netzwerkartigen Herstellungsprozesses
DE102018118471A1 (de) Vorrichtung und Verfahren zur Bereitstellung von Ersatzteilen eines Luftfahrzeuges
EP1610251A1 (fr) Méthode et système pour le traitement par ordinateur de fichiers de données
DE10103845B4 (de) Rechnersystem
EP1926019B1 (fr) Procédé d'échange de données et procédé de commande entre des composants logiciels et des composants logiciels réutilisables.
Stolzle et al. Impact of the implementation of Design for Circular Economy features on the product development process
DE102006021541A1 (de) System und Verfahren zur automatisierten Generierung, Verwaltung und Dokumententation von Gerätezusammenstellungen
WO2018206346A1 (fr) Procédé de traitement assisté par ordinateur de données de production numériques destiné à la fabrication d'un ou d'une pluralité de produits
DE102022204489A1 (de) System und Verfahren zum Erstellen einer Kostenkalkulation
EP1629401A2 (fr) Procede, dispositif et programme informatique comportant des elements de code de programme et un produit de code de programme destines a l'analyse de donnees utiles structurees selon une structure de base de donnees
DE102006037968B4 (de) Universelle und erweiterbare Datenverwaltung mit Beobachtungs- und Interprozesskommunikations-Mechanismen
WO2020094852A1 (fr) Dispositif et procédé pour l'attribution dynamique de données d'identification pour une configuration d'un système de configuration de produit
EP4160446A1 (fr) Analyse de capacité d'un composant dans une installation d'automatisation industrielle
WO2001037151A2 (fr) Procede de representation, d'integration et de commande par ordinateur de processus d'entreprises
DE10206285A1 (de) Verfahren und System zur markt- und anwendungsspezifischen Verwaltung von Optionen und Komponenten einer Produktplattform
EP3686740A2 (fr) Procédé de création des protocoles de processus

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

17P Request for examination filed

Effective date: 20100122

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: AL BA MK RS

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

Owner name: FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWAN

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: SIEMENS AKTIENGESELLSCHAFT

Owner name: FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWAN

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

Owner name: SIEMENS AKTIENGESELLSCHAFT

Owner name: FRAUNHOFER-GESELLSCHAFT ZUR FOERDERUNG DER ANGEWAN

17Q First examination report despatched

Effective date: 20160223

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

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: 20170307