1 / 48

Professor Joe Tah University of Salford

Knowledge-based decision support in integrated project modelling environments. Professor Joe Tah University of Salford. Presentation Content. Integrated Environments + Knowledge-bases Implementation of IFCs MAS Collaborative supply chain planning Conclusions. Integrated Environments.

saskia
Download Presentation

Professor Joe Tah University of Salford

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. Knowledge-based decision support in integrated project modelling environments Professor Joe Tah University of Salford

  2. Presentation Content • Integrated Environments + Knowledge-bases • Implementation of IFCs • MAS Collaborative supply chain planning • Conclusions

  3. Integrated Environments • Theme Decision support in integrated design and project management systems

  4. Problem Domains • CAD + Project Management • Rule-based knowledge representation • Motorway bridge construction planning and control • Case-based reasoning • Project risk analysis and management • Fuzzy logic

  5. Architecture

  6. Approach • Integration • Process modelling • Information modelling • Integrated project model database • Interface-enabling applications • Embedded knowledge-based decision support • Knowledge acquisition • Knowledge representation • Implementation

  7. CAD + Project Management • Integration of: • 3D-CAD • Project management • Using • UML-based OO modelling • OODBMS • KBS + Multi-Agent Systems Architecture

  8. CAD Sub-Problem Domain • CAD data semantic enhancement • building object types • building object dimensions • building objects material specifications • building objects topology

  9. Planning Sub-Problem Domain • Construction programme formulation • quantity determination • task and work load determination • resource selection • task productivity and duration estimation

  10. Information Model

  11. Knowledge representation • Rule sets • Setting structural components material specs • Elaborating component tasks into units of work • Determining the amount of work in tasks • Selecting appropriate concreting methods • Selecting resources for concrete placement • Selecting resources for fixing reinforcement • Selecting resources for erecting formwork

  12. RULES FOR SETTING ALL STRUCTURAL COMPONENT MATERIAL TYPES • FOR ALL StructuralComponent • IF SuperStructure.MaterialType is Reinforced • THEN StructuralComponent.MaterialType is Reinforced. • FOR ALL StructuralComponent • IF SuperStructure.MaterialType is Steel • THEN StructuralComponent.MaterialType is Steel.

  13. RULES FOR SETTING COMPONENTS WORK PACKETS • IF StructuralComponent.Location.SubORSup is Superstructure • AND StructuralComponent.Orientation is Vertical • AND StructuralComponent.MaterialType is Reinforced • THEN StructuralComponent.WorkpacketList includes (FixReinforcement, ErectFormwork, PlaceConcrete, StrickFormwork). • IF StructuralComponent.Location.SubORSup is Superstructure • AND StructuralComponent.Orientation is Horizontal • AND StructuralComponent.MaterialType is Reinforced • THEN StructuralComponent.WorkpacketList includes (ErectFormworkAndFalsework, FixReinforcement, PlaceConcrete, StrickFormworkAndFalsework).

  14. RULES FOR COMPUTING QUANTITIES OF WORK FOR EACH Unit of Work • IF StructuralComponent is Wall • AND StructuralComponent.Workpacket.UoWList includes (UnitOfWork = ErectFormwork) • THEN UnitOfWork.Quantity = 2 x (StructuralComponent.Breadth x StructuralComponent.Depth). • IF StructuralComponent is Beam • AND StructuralComponent.Workpacket.UoWList includes (UnitofWork = ErectFormworkAndFalsework) • THEN UnitOfWork.Quantity = 2 x (StructuralComponent.Breadth x StructuralComponent.Depth) + (StructuralComponent.Breadth x StructuralComponent.Width).

  15. RULES FOR CONCRETING METHODS SELECTION • IF MixingMethod is SiteMixed • AND TransportationMethod is Hoist • AND PlacingMethod is Skip • AND Quantity is Large • THEN ConcreteMethod is CONCMETH_4 • IF MixingMethod is ReadyMixed • AND TransportationMethod is Crane • AND PlacingMethod is Skip • AND Quantity is Large • THEN ConcreteMethod is CONCMETH_7

  16. PLACE CONCRETE OUTPUT RATES

  17. PLACE CONCRETE RESOURCE GROUP SELECTION RULES • RULE 4 (Select resource group to place site-mixed concrete to major works in mass concrete super-structure) • IF UnitOfWork.Name is PlaceConcrete • AND JobSize is Major • AND WorkLevel is Superstructure • AND MixingMethod is SiteMixed • AND ConcreteType is Mass • THEN UnitOfWork.LabourResgrp.ResourceID is PCLG4

  18. PLACE CONCRETE RESOURCE GROUP SELECTION RULES • RULE 7 (Select resource group to place ready-mixed concrete to major works in reinforced concrete super-structure) • IF UnitOfWork.Name is PlaceConcrete • AND JobSize is Major • AND WorkLevel is Superstructure • AND MixingMethod is ReadyMixed • AND ConcreteType is Reinforced • THEN UnitOfWork.LabourResgrp.ResourceID is PCLG7

  19. PLACE CONCRETE LABOUR RESOURCE GROUPS

  20. 4D Modelling – MicroStation/Microsoft Project Integration

  21. Case-Based Reasoning • Aim • Capture and re-use of project planning and control information. • Problem • Planning and control of motorway bridges

  22. Bridge Object Model

  23. Object Model – Task/Resource Details

  24. Case-based Reasoning Application

  25. Viewing Planning Data in MS Project

  26. Risk analysis and management • Knowledge representation • Hierarchical risk and action representation • Standardized terms for risks and actions • Risk and Action catalogues • Fuzzy risk representation and analysis

  27. Hierarchical Risk Breakdown Structure

  28. HRBS Code Type Scope Risk Centre Risk Risk Factor R.1.1.01.03.01 Internal Local Labour Productivity Fatigue R.1.1.01.03.02 Internal Local Labour Productivity Safety R.1.1.02.01.00 Internal Local Plant Suitability Suitability R.1.1.02.01.01 Internal Local Plant Suitability Breakdown R.1.1.03.01.00 Internal Local Material Suitability Suitability R.1.1.03.02.00 Internal Local Material Availability Availability R.1.1.04.01.01 Internal Local Sub-contractor Quality Quality R.1.1.04.02.01 Internal Local Sub-contractor Availability Availability R.1.1.05.01.00 Internal Local Site Weather Weather R.1.1.05.01.01 Internal Local Site Weather Temperature R.1.1.05.02.00 Internal Local Site GroundConditions GroundConditions R.1.1.05.02.01 Internal Local Site GroundConditions SiteInvestigation R.1.1.05.03.00 Internal Local Site Access Access R.1.1.05.03.01 Internal Local Site Access ExternalAccess R.1.1.05.04.00 Internal Local Site ExistingServices ExistingServices R.1.1.05.04.01 Internal Local Site ExistingServices BelowGround R.1.2.01.00.00 Internal Global Construction Construction Construction R.1.2.01.01.01 Internal Global Construction Complexity ComplexityOfWork R.1.2.01.02.01 Internal Global Construction Methods ConstructionMethods R.2.0.00.00.00 External External External External External R.2.0.01.00.00 External External Economic Economic Economic R.2.0.01.01.00 External External Economic Inflation Inflation Risk Catalogue

  29. Risk Management Process Model

  30. Object Model

  31. Fuzzy Associative Memories (FAM) FAM rules to determine risk magnitudes FAM rules to determine risk effects on performance measures

  32. Fuzzy membership functions

  33. Fuzzy inference and computations

  34. Risk Data Manipulation

  35. Risk Identification, Analysis, and Effects

  36. Risk Handling

  37. Lessons • OO modelling provided the basis for a common language for database & KB • Systematic knowledge elicitation and representation is key • Distributed computing standards absolutely essential for real-time processing.

  38. Emerging issues • IFCs appeared to be maturing • OODBMs failed to gain widespread use • Timely to revisit relational databases

  39. Recent Work • Build a project-model database on a relational database using IFCs • Explore data exchange between project-model database and MS Project • Make recommendations for future work

  40. IFC Modelling for Integrated Database

  41. MS SQL Server Database Implementation

  42. MS SQL Server Database User Interface

  43. MS SQL Server Database – MS Project Connection

  44. Findings • Structure of IFC suitable for automated data management and self-administration. • Overwhelming difficulties associated with implementing databases for use in IFC-compliant user-managed databases

  45. Recommendations • IfcProcessExtension unnecessarily complex and could be simplified • Practical requirements for planning, scheduling, and control software not fully supported and an update is necessary.

  46. Multi-Agent Systems • Characteristics • Autonomy - control own action • Social ability – interact with other agents • Responsiveness – perceive their environment • Pro-activeness – take initiative

  47. A partial view of the supply network sub-tasks

  48. Conclusions • Development necessarily evolutionary. • OO Standards-based common language is key, hence role for IFCs. • The potential for KBS is enormous and yet to be fully exploited. • MAS appear to provide a framework for integration in a Web Services future?

More Related