1 / 20

Radisson Plaza Hotel Minneapolis, MN September 17-19, 2007

Workshop BIM~ISO15926 Technical overview ISO15926. Onno Paap Integration manager Fluor Corporation. Radisson Plaza Hotel Minneapolis, MN September 17-19, 2007. The data model. An example of a very basic model is how we can tell what kind of object a particular 'physical object' is.

verne
Download Presentation

Radisson Plaza Hotel Minneapolis, MN September 17-19, 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workshop BIM~ISO15926Technical overview ISO15926 Onno Paap Integration manager Fluor Corporation Radisson Plaza Hotel Minneapolis, MN September 17-19, 2007

  2. The data model • An example of a very basic model is how we can tell what kind of object a particular 'physical object' is • The boxes are entity data types defined in the data model • Next to an identifier they have (almost) no attributes. • 'classification' is a relationship with two attributes: • 'classified' that (here) refers to a 'physical_object' • 'classifier' that (here) refers to a 'class_of_inanimate_ physical_object'

  3. The 15926 model

  4. ISO 15926 Part 4 Some details of ISO 15926 part 3 were merged with part 4: geometrical shapes based on STEP part 42

  5. mapping Trans formation Mapping an application to ISO 15926 Façade RDL Standard classes Façade OIM Application database Standard Product Models Mapping activity FaçademyProject ISO15926 Compliant data

  6. Mapping methodology

  7. Example specialized template in OIM(mapped from Part 7 Lite specialized Shortcut Template) <part7:ClassOfMultidimensionalObject rdf:ID="ST-VESSEL-3401-002"> <rdfs:subClassOf rdf:resource="http://www.15926.org/tpl#ST-3401"/> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="http://www.15926.org/tpl#possessor"/> <owl:allValuesFrom rdf:resource="http://www.15926.org/rdl#R414674"/> <!--VESSEL--> </owl:Restriction> </rdfs:subClassOf> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="http://www.15926.org/tpl#propertyType"/> <owl:hasValue rdf:resource="http://www.15926.org/rdl#R239239"/> </owl:Restriction> <!--NominalVolumeCapacity--> </rdfs:subClassOf> <rdfs:subClassOf> <owl:Restriction> <owl:onProperty rdf:resource="http://www.15926.org/tpl#basePropertyType"/> <owl:hasValue rdf:resource="http://www.15926.org/rdl#R549022"/> </owl:Restriction> <!--Volume--> </rdfs:subClassOf> </part7:ClassOfMultidimensionalObject>

  8. Typical exchange file in RDF/XML <rdf:RDF declarations> <. . . transmittal data . . .> A TYPICAL NODE <part2:ClassOfInanimatePhysicalObject rdf:ID="FPO-347621"> <!--myVessel (individual)--> <rdf:type rdf:resource="http://www.15926.org/rdl#R414674"/> <!--VESSEL (class)--> </part2:ClassOfInanimatePhysicalObject> AND A TYPICAL TEMPLATE INSTANCE <part2:MultidimensionalObject rdf:ID="ST-267634"> <rdf:type rdf:resource="http://www.15926.org/oim#ST-VESSEL-3401-002"/> <part7:temporalWhole rdf:resource="#FPO-347621"/> <part7:context rdf:resource="#COTWP-438834"/> <!--Project 4502 CR23--> <part7:beginning rdf:resource="#XSDT_20060306T1357Z"/> <!--March 6th, 2006 at 01:57pm GMT--> <part7:possessor rdf:resource="#FPO-347621-20060306T1357Z"/> <!--temporal part--> <part7:propertyType rdf:resource="http://www.15926.org/rdl#R239239"/> <!--NominalVolumeCapacity--> <part7:basePropertyType rdf:resource="http://www.15926.org/2006/02/part4#R549022"/><!--Volume--> <part7:numericalValue rdf:resource="#XSFL_50.75"/> (means: an xsd:float of '50.75') <part7:unitOfMeasure rdf:resource="http://www.15926.org/2006/02/part4#R567689"/> <!--m3--> </part2:MultidimensionalObject> </rdf:RDF>

  9. Application database Façade map Façades Façade query &map Other’s Façades

  10. Application database Application database Application database Application database Façade Façade Façade Façade map map map map Façades

  11. Application database Application database Application database Application database Façade Façade Façade Façade map map map map Façades ISO 15926 part 4 Reference data library EPC contractor 1 EPC contractor 2 Supplier catalog

  12. WIP - architecture Reference Data System http://rds.posccaesar.com RDS Temporary holder for ISO 15926 part 4 Reference data library (2 years) Also called ERDL (Epistle Reference Data Library)

  13. WIP - architecture FREE ACCESSWeb application rds.posccaesar.com RDS ISO 15926 part 4 12,000 classes POSC-Caesar lib 50,000 classes

  14. WIP - architecture • Enter new classes • Taxonomy • By certified users RDS • Classes approval • By domain experts • Enter new properties • By certified users • Starts from IDS project • Move properties to Object • Information Models (OIM) • By domain experts

  15. WIP - architecture Façade Façade Façade Façade Semantic Web interface for RDS FIATECH ADI project RDS project IDS project Evergreen operations RDS map

  16. WIP - workflow Façade Façade ISO 15926 Façade Façade WIP Reference Data Library Object Information Models Bentley class editor RDS Maintenance New entry Approval (by cert user) (by ISO)

  17. Between any two systems we may see the following types of data exchange causing problems: Query - exchange - hand-over

  18. Query - exchange - hand-over

  19. Reference Data Libraries

  20. Confederation of Façades

More Related