IP Library Granted Patent US 8,484,231
Granted Patent B2
US 8,484,231 · App. 12/914,184 · Granted Jul 9, 2013

System and method for data mapping and information sharing

Inventors: Cheng Jun Li (Beijing, CN); Henry Chen (Beijing, CN); Jian Geng Du (Beijing, CN); Conrad Bruce Beaulieu (Duluth, MN)
Assignee: Honeywell International Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,484,231
App. No.
12/914,184
Filed
Oct 28, 2010
Granted
Jul 9, 2013
Kind
B2
Art Unit
2161
USPC
707/756
Abstract

A process includes mapping a data format in an object in a source schema to a data format in an object in a destination schema. The process includes defining an attribute mapping, defining a relation between the data format in the object in the source and the data format in the object in the destination, mapping the data format in the object in the source to the data format in the object in the destination, and converting the data format in the object in the source to another data format within the source. When the object in the source has no analog in destination, a foreign object is introduced into the destination, and when the object in the destination refers to one or more dependent objects, one or more instances of referred objects are generated according to a predefined policy in the mapping.

Claims (45)

1. A process comprising:

mapping a data format in an object in a source schema to a data format in an object in a destination schema, wherein the mapping comprises a set of options comprising the data format in the object in the source schema has exactly one analog in the data in the destination schema, the data format in the object in the source schema has more than one analog, the data format in the object in the destination schema has more than one analog, the data format in the object in the source schema has no analog in the destination schema, and the data format in the object in the destination schema has no analog in the source schema;

defining an attribute mapping, the attribute mapping comprising a set of value options comprising an optional value, a constant value, an independent value, a simple value, an entity value, a specific query, and an assigned value;

wherein the independent value comprises an attribute that has no relationship with a specific object, the simple value comprises a number, a string, a logical value, and an enumeration, and the entity value comprises a composite object including simple values and other entity values;

defining a relation between the data format in the object in the source schema and the data format in the object in the destination schema;

mapping the data format in the object in the source schema to the data format in the object in the destination schema;

when the object in the source schema has no analog in destination schema, introducing a foreign object into the destination schema;

when the object in the destination schema refers to one or more dependent objects, wherein a counterpart is not defined in the source schema, generating one or more instances of referred objects according to a predefined policy in the mapping; and

converting data in the object in the source schema to the data format in the object of the destination schema;

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise Industry Foundation Classes (IFC) and building information modeling (BIM); and

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise ISO/PAS 16739 (Industry Foundation Classes) and OmniClass™.

2. The process of claim 1 , wherein the attribute mapping is associated and stored with the object mapping.

3. The process of claim 1 , wherein an implicit relation between an object in the source schema is mapped into a concrete object in the destination schema to represent an explicit relation.

4. The process of claim 1 , comprising mapping an abstract object based on a mapping of one or more derived types of the abstract object.

5. The process of claim 1 , comprising converting the data format in the object in the source schema to another data format within the source schema.

6. A non-transitory computer readable medium comprising instructions that when executed by a processor execute a process comprising:

mapping a data format in an object in a source schema to a data format in an object in a destination schema, wherein the mapping comprises a set of options comprising the data format in the object in the source schema has exactly one analog in the data in the destination schema, the data format in the object in the source schema has more than one analog, the data format in the object in the destination schema has more than one analog, the data format in the object in the source schema has no analog in the destination schema, and the data format in the object in the destination schema has no analog in the source schema;

defining an attribute mapping, the attribute mapping comprising a set of value options comprising an optional value, a constant value, an independent value, a simple value, an entity value, a specific query, and an assigned value;

wherein the independent value comprises an attribute that has no relationship with a specific object, the simple value comprises a number, a string, a logical value, and an enumeration, and the entity value comprises a composite object including simple values and other entity values;

defining a relation between the data format in the object in the source schema and the data format in the object in the destination schema;

mapping the data format in the object in the source schema to the data format in the object in the destination schema;

when the object in the source schema has no analog in destination schema, introducing a foreign object into the destination schema;

when the object in the destination schema refers to one or more dependent objects, wherein a counterpart is not defined in the source schema, generating one or more instances of referred objects according to a predefined policy in the mapping; and

converting data in the object in the source schema to the data format in the object of the destination schema;

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise one or more of Industry Foundation Classes (IFC) and building information modeling (BIM)); and

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise ISO/PAS 16739 (Industry Foundation Classes) and OmniClass™.

7. The non-transitory computer readable medium of claim 6 , wherein the attribute mapping is associated and stored with the object mapping.

8. The non-transitory computer readable medium of claim 6 , wherein an implicit relation between an object in the source schema is mapped into a concrete object in the destination schema to represent an explicit relation.

9. The non-transitory computer readable medium of claim 6 , comprising instructions for mapping an abstract object based on a mapping of one or more derived types of the abstract object.

10. The non-transitory computer readable medium of claim 6 , comprising instructions for converting the data format in the object in the source schema to another data format within the source schema.

11. A system comprising:

one or more computer processors configured for:

mapping a data format in an object in a source schema to a data format in an object in a destination schema, wherein the mapping comprises a set of options comprising the data format in the object in the source schema has exactly one analog in the data in the destination schema, the data format in the object in the source schema has more than one analog, the data format in the object in the destination schema has more than one analog, the data format in the object in the source schema has no analog in the destination schema, and the data format in the object in the destination schema has no analog in the source schema;

defining an attribute mapping, the attribute mapping comprising a set of value options comprising an optional value, a constant value, an independent value, a simple value, an entity value, a specific query, and an assigned value;

wherein the independent value comprises an attribute that has no relationship with a specific object, the simple value comprises a number, a string, a logical value, and an enumeration, and the entity value comprises a composite object including simple values and other entity values;

defining a relation between the data format in the object in the source schema and the data format in the object in the destination schema;

mapping the data format in the object in the source schema to the data format in the object in the destination schema;

when the object in the source schema has no analog in destination schema, introducing a foreign object into the destination schema;

when the object in the destination schema refers to one or more dependent objects, wherein a counterpart is not defined in the source schema, generating one or more instances of referred objects according to a predefined policy in the mapping; and

converting data in the object in the source schema to the data format in the object of the destination schema;

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise Industry Foundation Classes (IFC) and building information modeling (BIM)); and

wherein the data format in the object in the source schema and the data format in the object in the destination schema comprise ISO/PAS 16739 (Industry Foundation Classes) and OmniClass™.

12. The system of claim 11 , wherein the attribute mapping is associated and stored with the object mapping; and wherein an implicit relation between an object in the source schema is mapped into a concrete object in the destination schema to represent an explicit relation.

13. The system of claim 11 , comprising a computer processor configured for mapping an abstract object based on a mapping of one or more derived types of the abstract object.

14. The system of claim 11 , comprising a computer processor configured for converting the data format in the object in the source schema to another data format within the source schema.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 28, 2010
From: LI, CHENG JUN; CHEN, HENRY; DU, JIAN GENG; BEAULIEUU, CONRAD BRUCE
To: HONEYWELL INTERNATIONAL INC.
Reel/Frame 025211/0398 →
Continuity (1)
Related Publication 20120109988A1 · May 3, 2012