Presentation is loading. Please wait.

Presentation is loading. Please wait.

IT in the AEC Industry Fall, 2002 The Need for Data Exchange As computer applications became more numerous in every domain, the need and value for exchange.

Similar presentations


Presentation on theme: "IT in the AEC Industry Fall, 2002 The Need for Data Exchange As computer applications became more numerous in every domain, the need and value for exchange."— Presentation transcript:

1 IT in the AEC Industry Fall, 2002 The Need for Data Exchange As computer applications became more numerous in every domain, the need and value for exchange data between systems is an obvious benefit Preparing are report: Word, Photoshop, Illustrator, video clip Preparing a design: 3D Massing, detail construction model, rendering package, various analyses

2 IT in the AEC Industry Fall, 2002

3 IT in the AEC Industry Fall, 2002 Custom Translators DXF IGES ISO-STEP 1970s 1980s 1990s 2000s Evolution of Translator and Exchange Technology

4 IT in the AEC Industry Fall, 2002 What is a Building Product Model? §An electronic database or file §incorproates 3D geometry, possibly presentation geometry §includes functional, material specs, surface information, critical relations, esp. between multiple representations §a standard representation used for exchange between applications (CAD, engr., simulation, production) §interfaces between building aspect models, for system integration, system design/fabrication/assembly

5 IT in the AEC Industry Fall, 2002 The Basic Definition of the Building Product Model Subsystem detailing Material/Part Ordering(BOM) Fabrication Automation Architectural Design Analysis Applications Erection Planning Construction Scheduling Cost Estimation A common data structure that provides two-way exchange between muliple applications Site Planning

6 IT in the AEC Industry Fall, 2002 How is a Data Model Defined? 1. Scope defined 2. From process models, derive significant applic.interactions 3. From process models, define entities and attributes 4.Check with applications, to derive needed entities/attributes/structures 5. Define structure how entities are related 6. Test in trial translators 7. Document spec. as an open standard 8. Work with application vendors to implement

7 IT in the AEC Industry Fall, 2002 Current IT Efforts to Support Integration MEP Engr Actors Phase Structural Engr consultants Mech. sub struct. sub Other subs. Client Program Architectural Design General Contractor IAI Model (IFC2.x) architectural feasibility, design, facility mgmt. IAI Architectural Bldg. Model AISC-CIS/2 Steel Model AISC CIS/2 Model steel design and fabrication PCI-CPM project precast model PCI precast concrete design and fabrication project

8 IT in the AEC Industry Fall, 2002 CIS/2 Structural Steel Language Production Planning Steel Detailing What does CIS/2 mean to a design or fabrication shop? Fast design coordination Faster detailing/engineering fabrication automation

9 IT in the AEC Industry Fall, 2002 Complex Joints and Detailing

10 IT in the AEC Industry Fall, 2002 201: explicit draughting 202: associative draughting 203: configuration controlled design 204: mechanical design using boundary rep. 205: mechanical design using surface rep. 206: mechanical design using wire-frame rep. 207: sheet metal die planning and design 208: life cycle product change process 209: design through analysis of composite and metallic structures 210: electronic printed circuit assembly, design and manufacture 211: electronic test, diagnostics and remanufacture 212: electro-technical plants 213: NC process plans for machined parts 214: core data for automotive design processes 215: ship arrangements 216: ship moulded forms 217: ship piping 218: ship structures 219: dimensional inspection process planning 220: printed circuit assembly mfg. planning 221: functional and schematic representation of AEC process plants 222: exchange between design and manufacturing for composite structures 223: exchange between design and manufacturing for cast parts 224: mechanical product definition for process planning using form features 225: structural building elements using explicit shape representation 226: ship mechanical systems 227: plant spatial configuration 228: building services: HVAC 229: forged parts 230: building structural frame: steelwork 231: process engineering data GENERIC 41: fundamentals of product description and support 42: geometric and topological rep. 43: representation structures 44: product structure configuration 45: materials 46: visual presentation 47: shape variation tolerances 48: form features 49: process structure, property and representation APPLICATION 101: draughting 103: electrical applications 104: finite element analysis 105: kinematics 106: building core model 11: the EXPRESS language reference manual APPLICATION REFERENCE MODEL LANGUAGES - 12: the EXPRESS-I language reference manual NIAM - IDEF1x - EXPRESS-G IMPLEMENTATION METHODS 21: clear text encoding (file format) 22: standard data access interface (SDAI) 23 Early C++ bindings 24: Late c++ bindings CONFORMANCE TESTING 31: general concepts 32: requirements on testing laboratories 33: abstract test suites 34: abstract test methods ABSTRACT TEST SUITES 1201: ATS for 201 1202: ATS for 202 1203: ATS for 203 CONSTRUCTS 501: edge-based wireframe 502: shell-based wireframe 503: geometry bounded 2-D wireframe 504: draughting annotation 505: drawing structure and administration 506: draughting elements 507: geometry bounded surfaces 508: non-manifold surfaces INTEGRATED RESOURCES APPLICATION PROTOCOLS DESCRIPTION METHODS

11 IT in the AEC Industry Fall, 2002 STEP Architecture EXPRESS Data Modeling Language, description methods: generic and application integrated resources: re-usable EXPRESS construct s integrated resources Database Schema generators Implementation methods EXPRESS Graphical Language, EXPRESS-G description methods: Conceptual Model Application Reference Model (ARM), defined in: EXPRESS-G application protocols Require- ments Model application protocols: Application Interpreted Model (AIM): in EXPRESS Implement- ation Model physical file fomat or other implementation method(SPF) Implement- ation Medium Implementation methods

12 IT in the AEC Industry Fall, 2002 Software Exchange Process

13 IT in the AEC Industry Fall, 2002 Data Structure Data Structure Export Translator Source Application Import Translator Receiving Application Data Exchange Part 21File Part 021 Translator Product Model Conformance Class Subset Typical Data Exchange Process

14 IT in the AEC Industry Fall, 2002 XML and Product Models Design/Engineering /Manufacturing processes EXPRESS-based product model Complex engineering data, including geometry, behavioral properties, layout Business and product information design in text Business processes XML

15 IT in the AEC Industry Fall, 2002 Design Application 1 Design Application 2 Design & Analysis Application 3 Complex Exchanges: Design Application 4 Analysis Application 5 Analysis Application 6 Data Repository Some Example Types of Exchange

16 IT in the AEC Industry Fall, 2002 Criteria for selection: real-time vs. asynchronous exchange passing data vs. algorithms narrow vs. wide semantic domain internal network vs. Web-based open exchanges total passing of dataset vs. repository with incremental additions and extractions who will be responsible and maintain exchange SW? General Strategies for Exchange

17 IT in the AEC Industry Fall, 2002 Many possible ways to carry out Building Data Exchange: write to, then read from an ASCII file in some agreed upon format (DXF, IGES, STEP Part 21 file format) pass data between programs as C++ objects, wrapped as CORBA or COM objects (used in Intranet and file server networks) pass data in HTML or XML across Web (being used in e- commerce efforts) send JAVA objects that carry exchange data (approach being developed by Bentley) Some Example Types of Exchange

18 IT in the AEC Industry Fall, 2002 The Scope of the Precast Engineering Software Product Precast Product Model


Download ppt "IT in the AEC Industry Fall, 2002 The Need for Data Exchange As computer applications became more numerous in every domain, the need and value for exchange."

Similar presentations


Ads by Google