bim 360 with autocad civil 3d, autodesk vault ... bim 360 with autocad civil 3d, autodesk vault

Download BIM 360 with AutoCAD Civil 3D, Autodesk Vault ... BIM 360 with AutoCAD Civil 3D, Autodesk Vault

Post on 18-Jun-2018

221 views

Category:

Documents

1 download

Embed Size (px)

TRANSCRIPT

  • BIM 360 with AutoCAD Civil 3D, Autodesk Vault

    Collaboration AEC, and Autodesk Buzzsaw James Wedding, P.E. Autodesk, Inc.

    CI4500

    The modern design team does not end at the meeting room door, and by leveraging the full range of team collaboration tools from Autodesk, you can take your data full circle. In this class, we will look at delivering the promise of BIM 360 in the civil infrastructure profession by leveraging the interaction between AutoCAD Civil 3D, Vault Collaboration AEC, and Buzzsaw. We will start by exploring the internal team collaboration with Civil 3D and Vault, then submit drawings using Buzzsaw, and deliver feedback with the mobile AutoCAD WS platform

    Learning Objectives At the end of this class, you will be able to:

    Explain the concept of BIM 360 in the civil engineering framework

    Describe basic lifecycle concepts in the Vault Collaboration product

    Update and review data using Buzzsaw and WS platform technology

    About the Speaker James spent nearly a decade in the Dallas/Fort Worth land development industry before entering the Civil 3D consulting field in 2006. A graduate of Texas Tech with a BSCE in 1997, he worked as a design engineer focused on private development, designing small commercial to multiphase single family and master-planned communities during his time in the industry. One of the earliest gunslingers for the AutoCAD Civil 3D product, James has worked extensively with the Autodesk product team to shape and guide the software's development. A highly-rated repeat presenter at Autodesk University and co-author of the best-selling Mastering AutoCAD Civil 3D text, James joined the Autodesk team in 2010.

    james.wedding@autodesk.com

    www.twitter.com/civil3d

    www.autodesk.com/askjames

    mailto:james.wedding@autodesk.comhttp://www.twitter.com/civil3dhttp://www.autodesk.com/askjames

  • Insert Class Title as per Title Page

    2

    BIM 360 With every project, we consume data from a thousand sources and we share our creation with a

    thousand more. As a project moves from napkin sketch to paper to model to construction

    equipment, it will changes hands over and over, sometimes as a fax, sometimes as a courier

    package, sometimes through a digital markup. At every step of the way, every time theres a

    change in format, in owner, in process, in purpose, theres an opportunity for loss: loss of design

    intent, loss of detail, loss of clarity. All of these little losses lead to project breakdowns and

    inefficiencies.

    BIM 360 refers to the idea that a complete, accurate, digital model of our projects, providing

    access anywhere to key information across the entire project lifecycle. This view of the world

    leads to better decision make, new insights and predictability in the project delivery, and

    improved operational reliability and efficiency. BIM 360 is an idea though, and you need tools to

    make that idea a reality.

    Within the Architecture, Engineering, and Construction, (AEC) world and in the Autodesk view,

    the tools you need are bundled up in three segments: Design, Management, and Collaboration.

    Creating models is accomplished with tools like Revit, AutoCAD Civil 3D, and 3ds Max Design.

    Management is accomplished with the Vault Collaboration AEC data manament system.

    Collaboration (outside the company walls,) is accomplished using Buzzsaw, Design Review,

    and AutoCAD WS. Its an impressive tool collection, but with that many tools to understand and

    put together, the question quickly becomes, How do I make this all work?

    The Setup When you want to work with teams both internal and external, there are three major systems in

    play:

    1. The Design Software. This can be Revit, AutoCAD, Civil 3D, or any number of other

    design pieces.

    2. Internal Data Management. In this discussion, thats Vault Collaboration AEC.

    3. External Data Management. In this case, Buzzsaw

    Pulling all these pieces together isnt terribly complicated, but it does take some setup to really

    make it work! Lets take a look at the setup of each piece.

  • Insert Class Title as per Title Page

    3

    Design Software In the case of most Autodesk software you simply have to install the Vault client. When you do,

    youll see a new tab added to the ribbon as you see here:

    The commands along this

    tab are activated when you

    login to the Vault. You can

    see in this case, the Log Out

    button is active, meaning the

    user is already logged in to

    Vault. If these commands

    are greyed out, you need to

    login to the Vault system.

    Click the Log In button and

    youll see a dialog like this

    one. Note that you can use

    Windows Authentication if

    your Vault system is setup

    that way, and that you can

    toggle automatic login. This

    is a good suggestion if you dont share your computer with other users and you generally are

    working in a Vault environment.

    Once you have your design software setup to work with Vault, its important to do some work on

    the Vault system itself to make all the pieces work together smoothly.

    Setting up the Vault System Before you can begin building and creating an effective Vault Collaboration system, you need to

    know whos who and think about what you want them to be able to do. In this discussion, we

    typically need to setup Users & Groups, Categories, and Lifecycles.

  • Insert Class Title as per Title Page

    4

    Users & Groups To manage data security, you have to assign rights and privileges to some users while

    withholding them from others. In Vault, we typically do this with Security Groups. In this

    exercise, well create a basic security group.

    1. Launch your Vault Collaboration application and login as a user with administrative

    privileges.

    2. Select ToolsAdministrationGlobal settings to display the Global Settings dialog.

    3. Change to the Security tab if necessary, and click the Groups button on the right to

    display the Group Management dialog.

    4. Select New Group from the toolbar to display the group dialog shown here:

    5. Enter a group name and an e-mail if you have a distribution list setup for the group.

    6. Click on the Roles button to display the Add Roles dialog.

    7. Check the Document Editor (Level 2) option and OK to close the dialog.

    8. Click the Vaults button to display the Add Vaults dialog.

    9. Check the appropriate Vaults for access and click OK to close the dialog.

  • Insert Class Title as per Title Page

    5

    10. Click Add to the right of the Group Members to display the Add Members dialog. Select

    an appropriate user, click the Add button, then close the dialog by clicking OK.

    11. Click OK to close the Group dialog, then the X in the upper right to close the Group

    Management dialog.

    12. Click Close to exit the Global Settings dialog.

    If you click OK without adding a person to your group, Vault will complain about not having

    members. For this reason, Ive often found that creating a dummy account that no one actually

    logs into is a nice placeholder and will keep your hair pulling to a minimum. Youll want to

    actually assign users to groups as youre creating them, but I like having the containers in place

    first.

    When youre planning your Vault configuration, think before you create group after group. As

    youll see later, for every group you have, youre adding branches on the decision tree. Keeps

    your groups to the minimum you need and your life will be better. Now we have some of the

    players established, lets look at how theyll work with our Vault information.

    Data Lifecycles in Vault Collaboration Most firms have an ad hoc lifecycle management and security system. Almost every firm has a

    horror story of a user editing files they shouldnt have, usually leading to a costly change or a

    change in employment status. Some firms go through the hassle of setting up separate data

    shares, or even isolating files between groups, requiring survey to e-mail surface information to

    the engineering group. Regardless of the methodology, most current systems are onerous and

    cause at least as many problems as they solve.

    With Life Cycles in Vault Collaboration, you can create both a security model and an approval

    process in a semi-transparent model. A simple lifecycle could be something as simple as this:

    A bit of data is created, checked by the same group that created it and is then released for use

    by other groups. Even with something as simple as this, there are a lot of questions:

    Who can edit an object thats in a Work in Progress state? What about when its

    Released?

    Who can view and object in a WiP state? Released?

    Who can move an object from WiP to Release? What about pushing it back?

    WORK IN

    PROGRESS RELEASED

  • Insert Class Title as per Title Page

    6

    Even with the most basic lifecycle setup, you have to consider three major permissions: Edit

    Privileges, View Privileges, and Change State Privileges. Along the way, you can also make

    decisions about how a file should be modified with labels, updated with a new revision number,

    or published to a web server for external review.

    Lets take a look at a more complex process, maybe something like a topographic survey might

    go through.

    In this exercise, well setup this basic Lifecycle, establishing the states as show

Recommended

View more >