Model-Centric Quality Assurance in the AEC Environment

1. Model-Centric Quality AssuranceIN THE AEC ENVIRONMENT Danny L. Kahler, P.E. Session T43 ASQ National Conference for Design & Construction and Energy & Environmental Divisions September 20th, 2005 San Antonio, Texas

2. Speaker Introduction • Danny L. Kahler, P.E. • Civil Engineer • Bridgefarmer & Associates, Dallas, TX • 20 years of engineering experience • ASQ Senior Member • ASQ CQA, CQM, CQE and CSQE

3. Vocabulary • Model - A simplified representation of a system at some particular point in time or space intended to promote understanding of the real system • System – A system exists and operates in time and space • (Definitions obtained from Society for Modeling and Simulation International)

4. Vocabulary (Continued) • Model Centric Design – All significant design processes extract information from and update changes to a common product model. The product model should be based on an organization-wide protocol.

5. Why “Model-Centric”? • Multiple Agencies • Tighter Schedules • Design/Build Project Teams • Increased Cost of Errors • Increased Cost of Disputes • Increased Cost of Personnel • Fewer “Seasoned” Engineers

6. Who already does “Model-Centric”? (AT LEAST TO A GREATER EXTENT THAN AEC) • Defense and Aerospace • Industrial and Process • Software Developers

7. What were we doing in the past? • In the past, the “model” was ink on mylar • The technology was simple enough for everyone • The design environment had rules that everyone learned over time • It forced technical people to “see” the model in their mind • It was difficult to constantly change the model

8. What motivates us to do “Model-Centric” today? • Desire to reduce cost • Desire to reduce post-design “fixing” • Desire to reduce miscommunication • Informed and demanding customers

9. Is Model-Centric about Software? • Software packages are tools. Model-centric is about how we work with each other and make choices based on a common view of the project data • The goal is to train organizations to make full use of new potentials regardless of what tools (or software) they choose to invest in.

10. Plans Only Plans Visualization Plans --> Model Roundtrip Engineering Plans <--> Model Model-Centric Plans <-- Model Model Only “What’s a model?” “The plans build the model” “Plans and model coexist” “The model builds the plans” “Pure design” (no more drafting plan sheets) Evolution of Model-Thinking

11. What is Model-Centric Quality Assurance? Model-Centric Quality Assurance occurs when the evaluation of adequacy is based primarily on the integrated review of the source model rather than inspection of individual views (plans)

12. What kind of QA systems do we normally see today? • Document Based • Multiple Iterations of Construction Plans • Heavy Focus on Appearance • Frustrating Amount of “Drafting” Comments • Reviewer Reward/Recognition based on Volume of Comments Generated

13. Can we do Model-Centric QA now? Maybe. • Many agencies have set standards for electronic model information (sometimes hidden in CADD standards) • Many agencies require consultants and contractors to use only pre-approved software

14. Example: TxDOT Plans Manual Design Files • Complete all design in one or more master design files, not individual sheets. All master design files should be full scale, real world coordinates. • Multiple master design files (TOPO, ROADWAY, DRAINAGE, BRIDGE, etc.) allow several designers to work on different parts of the project at the same time while referencing each other's work. • Place all features at exact coordinates, not eyeballed • Attach master design files to sheets as a reference file

15. Model-Centric QA Experimentation • Bridgefarmer & Associates served as the Quality Assurance reviewer for a major design-build project in Texas • All submittals to QA contained design model information (in Microstation and Geopak) in parallel with traditional plan sheets. Around 80% of all design comments came from direct review of the model.

16. Some Model Transfer Happens Today • Some contractors, who have access to the source design files, report they often have fewer errors than the signed and sealed paper plan sheets • The plan sheet errors are usually caused by incorrectly labeled design features

17. Model-Centric Construction QA • Inspection specific to location • Sequence of site through time • Construction GIS • True “As-Built”

18. How can we improve Model-Centric QA? • By using Software Quality Concepts: • Validation • Verification • Accreditation

19. VALIDATION • Validation: The process of determining the degree to which a model is an accurate representation of the real-world from the perspective of the intended use of the model • Are we doing the right thing?

20. VERIFICATON • Verification: The process of determining that a model implementation accurately represents the developer’s conceptual description and specifications. • Are we building the thing right?

21. ACCREDITATION • Accreditation. This is the official certification that a model is acceptable for use within the context of a specific objective. • Is it what the customer wanted?

22. Taxonomy of Model QA • Fit • The static 3-D Integration of the Project • Flow • Things the project must transport; storm drainage, sewage, motorists • Function • Ability of subsystems to do their jobs; signals, gates, message boards, roadway signs

23. How can Model-Centric thinking reduce costs? • Fewer review documents • Faster turnaround • More efficient use of manhours • Decreased communication errors • Decreased project risk • Early resolution of disputes

24. Future of Model-Centric QA • Contractor-Driven – the contractor as a design-build customer will push for ways to improve profit margins. • Stress of Change – some will adapt and others won’t • Real-time reviews – why wait for a submittal to check the design?

25. Example of a Model Protocol LandXML – Powerpoint presentation from www.landxml.com

26. LandXML An emerging XML data standard format for civil engineering and survey data used in the Land Development and Transportation Industries Nathan Crews Software Researcher, autodesk, Inc.LandXML Principal Architect, www.landxml.orgaecXML Infrastructure Facilitator

27. LandXML: Design Data Focus • The primary goal for LandXML is to specify an XML format for civil engineering design and survey data to: • Transfer engineering design data between producers and consumers. • Provide a data format suitable for long-term data archival. • Provide a standard format for electronic design submission.

28. LandXML: Organization • Initiated in December 1999 by Autodesk and EAS-E initiative members • Autodesk provides funding for www.landxml.org • Autodesk contributes primary authors and documentation resources • Initial LandXML schema derived from EAS-E initiative. • Engineering And Surveying – Exchange • Open communication between member companies and government agencies.

29. Global Participation

30. Government and Private Sector Participants • Nebraska, Florida and many additional State Departments of Transportation. • AASHTO • Federal Highways Administration. • US Environmental Protection Agency. • Land Information Systems New Zealand. • Langan Engineering and Environmental Services. • Clough, Harbour and Associates LLP.

31. Extending the use of Design Data <----------------- LandXML Data ----------------> Pre-DesignData capture and analysis Typically in various format CAD/DesignEngineering and design data Typically specific drawing and project file format(s) Post-DesignConstruction, scheduling, maintenance, and public use Typically in many different formats

32. LandXML: Design Data Model • Alignments - Road centerline line, curve and spiral geometries • GradeModel – 3D road surface data • Roadways – road data model • PipeNetworks - Hydraulic pipe and structure elements • Project - Project name and description • Surfaces - digital terrain models • Units - Linear, angular, area, time, temperature, pressure, diameter, volume, flow and velocity.

33. LandXML: Survey Data Model • CgPoints - Cogo Point elements • CoordinateSystem - Cartesian or earth based georeferenced coordinate system. • Monuments – Survey monument data • Parcels - Parcel or subdivision lots • Survey - Survey data collection parameters and measurements

34. LandXML: Design Data Exchange Desktop Browser/Web Authoring Application READ and WRITE data to/from LandXML data format LandXML project file Mobile

35. LandXML: Design Data Increase project efficiency - Provide design data for IHSDM road design validation. • Streamline design-build by providing accessible design data to survey field instruments. • Provide a design data additions for GIS databases.

36. LandXML: Design to Field Design Creation Design Validation IHSDM LandXML Field Staking

37. LandXML: Ancillary uses for data • Source data for quantity take off, cost estimation. • Source data for custom calculations and reports. • Source data for 3D project visualization.

38. LandXML: Potential Secondary Uses Application X Application Y Application Z LandXML Project File 3D Graphics Web-Based Reports

39. LandXML: Data Archival Enterprise Database Server Authoring Application READ and WRITE data to/from LandXML data format LandXML project file Archive Database Server

40. LandXML: Schema Status • Commercial Software available from Autodesk, Eagle Point and Bentley. • Version 1.0 posted. • Based on W3C XML Schema Recommendation May 2, 2001. • Schema documentation effort underway. • Meets original design goals: • Element uniqueness, referencing and re-use. • Data/file size is manageable.

41. LandXML: What is next? • Continue schema development and acceptance. • Continue close working relationships with AASHTO, FHWA and ISO standards committees. • Adjacent XML schema element re-use and interoperability. • aecXML • OpenGIS Coordinate Systems • Continued expansion of software application and hardware support.

42. Where to Get More Information • www.landxml.org • State Highway Agencies • Software Vendors; Bentley, Autodesk, Trimble, etc • kahler@bridgefarmer.com

43. Questions?