© 2012 Autodesk

The Mechanics of Metro Survey: An AutoCAD® Civil 3D® Infrastructure Case StudyTench TilghmanPresident, MoreCompetency, Inc.C13083

© 2012 Autodesk

Class Summary

C13083It takes more than vision when you are first on the ground and last to leave in today’s budget-tight, target-rich environment at the "silicon heart" of the world’s economy. Can the survey department of a large urban/suburban metropolitan area teach us about how to practically implement, learn, and employ AutoCAD Civil 3D software? The department's ecosystem is a political and complex technical network that includes every known form of municipal infrastructure—from the oldest state historic sites, high tech campuses, and a large international airport. Their historic and demanding customers work in a variety of CAD design and GIS software from AutoCAD® to Bentley® MicroStation® and beyond. They have gigabytes of historical data, multiple input data forms, and more output standards, reports, and changing job requirements than anyone ever wants to deal with. That’s the job. How do they and the Civil 3D survey features deliver the technical muscle, quality assurance methods, standards flexibility, and productivity to get it done?

© 2012 Autodesk

Learning Objectives

At the end of this class, you will be able to: Identify the mission-critical standards opportunities for survey customers and

know how to implement them

Discover the best functional workflows for survey work inside of AutoCAD Civil 3D and mentor your staff to use the workflows

Follow the practical steps that allow field crews, office staff, and project managers to work together effectively

Deliver Building Information Modeling (BIM) for infrastructure results with an improved ability to publish on demand

© 2012 Autodesk

Metro Survey Case Study Background

© 2012 Autodesk

City of San Jose

Located in the Heart of Silicon Valley

Third-largest city in California Population of 960,000+ About 178 sq. miles of area Founded in 1777 Grew rapidly in the last 5 decades Growth slowed significantly at the

turn of the century

© 2012 Autodesk

The City Survey Department

3-4 full time field crews 5-6 “CAD” Staff 3 Management Staff

All employ CAD software Previously employed Microstation

3 staff members knew AutoCAD Lieca Survey Equipment Trimble Data Collection and

Survey software

Customers include external City departments and other agencies

Diverse customer needs in both data content and publishing demands

Few departments employ the same CAD software in platform or release

City employs 3 distinct GIS platforms

© 2012 Autodesk

The Challenges

No in use city-wide CAD Standards Customers employ different CAD

design software platforms in multiple different releases

More infrastructure maintenance projects More projected work with less staff

due to reduced budgets More diverse work in smaller scale

projects

Staff employed 5+ year old CAD software Many staff had employed the same

software processes for a decade Staff Retention and Motivation

Staff Retirement Loss Issues Growing Age and Experience Gap Availability of Qualified Staff

External Customer Drivers Little Control of Demand and Work

Load

© 2012 Autodesk

Mission Critical Decisions

© 2012 Autodesk

Why Adopt AutoCAD Civil 3Dand Change Platforms? Commercial and Governmental Platform Popularity

National CAD Standards compatibility and capability

Staff Retention and Availability

Increased Survey Data Input and Output Flexibility

Compatibility with existing (planned) equipment and other software

© 2012 Autodesk

A Mult-year Project Approach

Year 1 Adopt NCS Graphic Standards to drive “customer” adoption of the same Train Staff Continuously

No time for all at once Cost control customization and maintenance

Standard “Product” Pilot project field to finish capability

Develop Civil 3D Work flows and production capacity

© 2012 Autodesk

Multi- Year Project

Year 2 Full project production in AutoCAD Civil 3D Development ACAD and DGN delivery capability

Driven by Customer Demand Improve field gathering and internal QA processes Increase staff internal production and publishing capabilities and skills

Year 3 Fully integrate ACAD and DGN digital deliverable output

Driven by Customer Demand Deliver more field gathering capacity for GIS integration

© 2012 Autodesk

The National CAD Standard (NCS)

Path of Least Resistance Not Vendor or Platform Specific Final Deliverable Based

Does Not confine production work to a methodology Most Standard “Decisions” are Published

Layer|Level, Block|Cell, Colors, etc Standard UDS Project Structure Standard UDS Deliverable Structure

Recommendations for Publication not Laws Available Conforming Product Solutions

© 2012 Autodesk

Work The Same – Publish on Demand

BIM or whatever we call it is DATA centric Fits into the Survey mindset and deliverable

creation

Model-based software – Civil 3D is DATA centric Civil 3D Features hold and collect data

Style produces non-scale dependent linework representations

Label Styles produce non-scale dependent annotation driven by data

© 2012 Autodesk

Style Based Management & Workflow

AutoCAD Civil 3D Employs Style based Management Employ one set of Styles to perform the work Employ other set(s) of Style to publish the work if required Civil 3D Templates provide a method of delivery

A Data By Style Approach is NOT CAD Drafting Training and training reinforcement is required

More Data Maintenance and Style Changing Skills Production work (data assessment and cleanup) requires:

A Set of meaningful Style QA “Tools” Deliverable Production may require:

Different and more Limited Sets of Style Tools

© 2012 Autodesk

Work & Publish

Production Work A richer Set of meaningful Style QA

“Tools” Tool Resources Expose to users

Consistent Style Name Rules Rule based systems NCS Like

Consistent and VisibleStyle Documentation What is the purpose of the tool

Publication Smaller Style Sets

More Specialized Style Sets Style Neutral Data Storage

Data Features stored in “Standard” Upgrade without Custom issues Transparent to Style change

Use the Same Names – Get different graphic results

© 2012 Autodesk

Development

© 2012 Autodesk

Development Projects

Template Development A Continuous Process

New projects and tasks require new Tools New releases add new Features, Workflows, and Processes

A Project based Structure & Process

Manages Complexity by Simple Separation

Produces a Transparent, Robust, and User Useful Resource The “Known Good”

© 2012 Autodesk

The Project is a Sandbox

Iterative PDCA Plan|Do|Check|Act

Style QA Testing requires “real” drawings and data Copy data to the Sandbox and play

Publish development requires out to Published validation Style Details Publication Process Details

© 2012 Autodesk

Production Workflows

© 2012 Autodesk

How Survey in Civil 3D Works

© 2012 Autodesk

Feature Specific Demonstrations

Points Description Key Sets & Priority

The Override Strategy – Force Points & Override The Priority Strategy – Force Nothing, Something, or Everything

Key Strategy & Concepts Not Keys – Smarter Logic that Works for You Format Language Translator

Point Group Mechanics & Priority PG Text file resources

Figures The Integrated Figure Prefix Db(s) Code Set Styles

© 2012 Autodesk

Point it Out and Figure It Out Demo

© 2012 Autodesk

Survey Db Edit Mechanics Demo

© 2012 Autodesk

Surface QA Demo

© 2012 Autodesk

Linear Feature Demo

Alignments & Profiles By Dref, By Object, By XML, By Design Methods Best Fit Methods

Parcels Site Parcels From Out Down to In LandXML to XREF Sharing

© 2012 Autodesk

Open Questions & Answers

© 2012 Autodesk

Take Away Summary

Work the Same & Publish on Demand Functions in the real world Focus on Production BEFORE Publication

Publication is easier A Project as a Sandbox

Do the QA Work Make the Work Visible and Useful to all

Deliverable Processes Image Publication is safer, easier, and faster Digital Deliverables are Produced By Feature

SaveAs is NOT Export To

© 2012 Autodesk

Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2012 Autodesk, Inc. All rights reserved.