LF5038 - Location, Location, Location-Handout

Location, Location, Location: 50 Models, 50 Contributors, 20 Companies, 5 Buildings, and 1 Site
Jon Anunson URS Corporation Marla Caserta URS Corporation
LF5038
Location can become a big issue in an Autodesk Revit project. How do we collaborate between multiple offices? How do we exchange data, coordinate building position, link models, and keep the chaos away when everyone is working in multiple companies, locations, platforms, and units? We will look at lessons learned, and the management tools and techniques used to settle issues of model linking, central file sharing, shared coordinate systems, Revit Server, and model content.
Learning Objectives
At the end of this class, you will be able to: List the capabilities of Revit Server and Autodesk Project Bluestreak Mobile to aid with intercompany communication Plan model contributions for multiple offices to collaborate successfully on a multi-firm project Explain how the shared locations and other file formats are affected by the use of Revit Server Describe how Revit Server can function within a multi-location company to help share models
This is a big-picture topic, concentrating on the options, the pros & cons, and some advice from experience. While the support materials include specifics regarding technical approach, the true focus will be on the decisions made while planning a project and their effect on the teams success.
About the Speakers

Jon Anunson, AIA, NCARB, BIM Coordinator, URS Corporation. Jon.Anunson@URS.com
A registered architect and database programmer/software engineer, Jon has 30 years of experience in computer graphics, 3D Modeling and programming and 20 years of experience in architectural design and production. He's worked with enriching 3D design models and documents with client, design, and construction data for over 15 years, and has been an active Autodesk Revit user since version 1.0. Jon has coordinated BIM implementations of complex architectural and engineering projects such as hospitals, airports, and secure and federal projects ranging in size up to millions of Square Feet. He consults on projects with a variety of special needs including 3, 4, and 5-D construction coordination, complex delivery methods, the utilization of IPD Protocols and model collaboration, and the integration of specialty data and computational needs. He has presented BIM concepts and techniques to various national and international trade & industry groups, local and regional AIA meetings, and at university and college lectures and symposiums.
Marla Caserta, AIA, Cleveland OH BIM Leader, URS Corporation.
Marla.Caserta@URS.com
Marla is a registered architect and BIM manager for the URS Cleveland office with 13 years of professional experience. As project architect she has produced and managed BIM deliverables from schematic design through construction administration on projects ranging from small renovations up to 1
LF5038 Location, Location, Location, Location:

50 Models, 50 Contributors, 20 Companies, 5 Buildings, 1 Site
million square feet of new construction. As BIM manager she has helped develop plans to integrate project standards and execution plans for projects of all sizes.
URS Corporation
www.urs.com
URS uses Building Information Modeling (BIM) to deliver better documents and design better facilities. BIM gives us the tools to understand project and program requirements, to visualize, test, and evaluate our designs, and to lead the construction effort to the best possible conclusion. Because our BIM models are three-dimensional, this also allows us to create more comprehensive and better coordinated documents. Building architecture and systems can be evaluated in 3D space, and in simulations to better enhance the synergy and coordination between systems. Construction conditions that are unaddressed in 2D documentation are made more visible, and fewer coordination issues need to be addressed during construction. A 3D BIM model also enhances our ability to communicate and collaborate with you, the client, so that we can be more efficient in understanding your requirements and gaining your approval. By using BIM we ensure our ability to create successful, beautiful and functional buildings and satisfy our clients. URS has years of experience delivering BIM-based design and construction data for a wide variety of project types and sizes, up to millions of square feet, including Hospitals, schools, and manufacturing. We have delivered BIM deliverables to private, public and government agencies with a broad range of data and integration requirements. We can meet your requirements for modeling, interoperability, delivery and coordination for your BIM or Integrated Delivery project.

Session Outline;
Subject Start Duration
Introductions
Location 4; Why Location is still so critical in a digital project
0:00
0:10
Location 1 (Where is your team?)
0:10
0:10
Understand how the team will communicate and collaborate on models from different locations, networks and cultures.
Location 2 (Where are your Files?)
0:20
0:10
Understand how the files will be transferred and/or shared. How the whole projects data must be assembled from information from multiple locations
Location 3 (Where is the Data?)
0:30
0:10
Creating data that is compatible across multiple files from multiple sources, and with the end deliverable can be a challenge. Understand how data must be organized within individual files.
Location 4 (Where is the Building?)
0:40
0:10
Locating model data relative to other model data when involving multiple software/file formats, coordinate spaces, units, and size/flatness limitations can be very tricky!
Conclusion, Location (Where is your plan?) Q&A Thank you for attending!
0:50 0:55 0:00
0:05 0:05 1:00
Complete the AU Conference Survey at a survey station and receive an AU 2011 T-Shirt. You (attendees) will receive a link (via email) for to evaluate this session, and surveys can also be completed on a survey station here at the event. Contact me with follow-up questions, suggestions, or other requests @ jon.anunson@urs.com.

Session Materials
Introductions
Session Overview Speaker Introductions Location 4 (Location hyper-cubed) Why Location can still become so critical in a digital project. In the digital age, weve become accustomed to being able to ignore location. We can email drawings, IM or Skype conversations, post documents to web portals for collaboration we dont need to worry about location! Until a project reaches a certain size, in terms of team, site, model, file, and / or distance... then location becomes the critical factor. We have standards for delivery, talented architects and engineers, dedicated partners, and this is enough until the location factor becomes a critical element. Then we need a plan.
Project Examples
The following (real) projects describe situations where location becomes critical in a number of different ways. Hospital Project: URS Engineers of Record, Separate Design Architect, Models delivered to contractors, 2 Million Square Feet. Models: All Revit, All Disciplines, 6 Buildings, 7 Sections, 6 Floors, 9 model disciplines Team: Seattle, Chicago, Cleveland, Columbus, Grand Rapids, New Orleans, Baton Rouge Convention Center and Office Tower Project: URS Record documents, separate Design Architects, Historical preservation architects, Landscape architects, Models delivered to CM, 1+ Million Square feet, 3 City blocks, sub roadway, connecting to historical structures. Models: DGN, Revit, DWG, STL, IFC Team: 25 Model contributors, multiple staged authorship handoffs; design, record/construction documents, design-assist contractors, fabrication.

High-rise Development 26 story, 2-tower, 1 city block, split level with parking structure under landscaped plaza on extreme fast-track. Separate firms for Architecture, Engineering, Landscape, Civil, with fabrication models for steel, foundations, and curtain walls. URS Architects of Record, with separate design architects. Models: STL and RVT, MEP in RVT to DWG + Civil 3D. Phased fast-track delivery meant combining design models with fabrication and/or as-built models. Team Light Rail Transit System Project: 8 rail stations/renovations by 2 different designers, documented by 4 offices, Civil in DWG + Track alignments, Models DGN track alignment, DWG topography, RVT structures, DWG Deliverable, located in real coordinates along some 20 KM of track. Team: Each station designed and documented in separate RVT file in 3 locations, Civil in a fourth, rails in a 5th.

Location 1 (Where is your team?)

Understand how the team will communicate and collaborate on models from different locations, networks and cultures.
When planning a project that involves model collaboration from multiple locations, take into account time zones, drafting/model setup standards, Titleblocks and shared parameters. These are things that can be handled up-front, or become a continuous time-sink for the project if everyone starts with differing assumptions. Consider creating a Standards model that includes the schedules and shared parameters, materials, title blocks, symbols, text styles and line weights you expect everyone to use. This can be created before a project begins to eliminate the setup lag on a complex project. Where are your employees? Even inside the firewall, you still need to know where your data needs to go! On-Site and remote workers o How do they connect to, modify, and return with the data? Multiple departments Will they talk? How can you ensure it? Multiple Addresses They may as well be consultants!
Implications Communication is required during model collaboration, more communication than a traditional project. BIM does not solve communication problems, it exposes them. Always-On communications are a must (Instant Messaging, Skype) Consider Project Hoteling Provide project-based workspaces that users occupy for specific projects. Include in the project hotel space the computers, and interactive equipment to best facilitate design and construction conversations that include all disciplines, and consultants and contractors as well. This is an excellent way to build up a SWAT team, and supports the interaction and collaboration needed to succeed in BIM and/or Integrated delivery. Tradeoffs Flexibility in staffing and consultants versus fluid communications. The bandwidth of communication for staff collaborating on a BIM project is very large. Organizational Points Project communications for distributed teams (Goals, Deadlines, and Deliverables) must be as clear as possible from the outset.

Utilize conference calls, web meetings, instant messaging and SharePoint Connections and communication within the team cant be overvalued. Make everyone use their instant messenger. Hold regular BIM progress meetings (at least weekly), and keep your files accessible to everyone using Bluestreak and/or SharePoint or Buzzsaw/Constructware. Manage remote workers differently. Managers must utilize the same communications tools that the project team utilizes to stay in touch when using Revit. Web Meetings can be used to share desktops and discuss current progress. DWF Markups provide effective redline vehicles for remote workers. Instant messaging applications keep workers talking to each other and to their manager, and all project files must be made accessible to everyone. This may also require managers to involve IT at an early project stage to prepare the project folder to accommodate remote workers. Project Management: SCRUM For a more complete definition of SCRUM, See the SCRUM In under 10 Minutes video on YouTube or 5min.com. The video does a nice job of quickly explaining the SCRUM concept. SCRUM can apply well to the concept of developing a set of architectural documents and is also good for managing a more iterative development process as required by a BIM workflow. Scrum is a rugby term, and is used to describe this process as an analogy to a rugby scrum where players all bundle together and attempt to push the ball forward as a group Product Backlog: A well designed Product Backlog would be equivalent to an excellent set of best practices, where each item that could potentially be included in a perfect document set is outlined; What a finished product would look like, what tools to use, how to use the tools, and when it should be done, by whom. The Product Owner The product owner roll equates to the project principal and/or project manager, selecting items from the backlog that reflect our contract and the needs of the design. Scrum Master This is the Project manager, working to the plan, sometimes with the aid of a facilitator/ communicator. Release Backlog The PM/Scrum Master places the desired project components into a plan by 7

phase, each phase of the project equates to a 'release'. There would generally be 4 releases in an architectural project, each divided into 4 Sprints, the last Sprint in each release being Quality Control Review. 01 Programming Sprint 1 - First Sketches, Initial Pass Sprint 2 - Coordinated refinement Sprint 3 - Redevelopment, Client Approval Sprint 4 - Re-Coordination, Defect Log Sprint 5 - Quality Control, Client Approval 02 Schematic Design Sprint 1 - First Sketches, Initial Pass Sprint 2 - Coordinated refinement Sprint 3 - Redevelopment, Client Approval Sprint 4 - Re-Coordination, Defect Log Sprint 5 - Quality Control, Client Approval 03 Design Development Sprint 1 - New Information Sprint 2 - Coordinated refinement Sprint 3 - Redevelopment, Client Approval Sprint 4 - Re-Coordination, Defect Log Sprint 5 - Quality Control, Client Approval
04 Construction Documents Sprint 1 - New Information Sprint 2 - Coordinated refinement Sprint 3 - Redevelopment, Client Approval Sprint 4 - Re-Coordination, Defect Log Sprint 5 - Quality Control, Client Approval 05 Construction etc.... 06 Occupancy etc....
Sprints Here things diverge a bit. To be successful, a facility design must be iterated through multiple times as information and coordination is refined. When he says in the video that each sprint results in a 100% ready product, we would have to diverge and say that each sprint results in the documentation of all the information available at the time. Many backlog items would be revisited several times in the project, perhaps even in different sprints of the same phase. Burndown Chart Similar to how most firms currently watch project progress. The information-gathering technique he describes at about 5:40 in the video for collecting the data for the burndown chart could be built into the sheet schedule for a Revit file: As users re-define their time estimates per sheet, the burndown rate can be projected and compared to the original estimate. Defect Backlog Code Issues, Client approval/input, etc. By keeping these items separate, we also have a tool to show the owner what their actions do to impact project progress. SCRUM is a management model that can help with projects that have common properties for building design: One-of-a-kind solutions, created by many authors, collaborating on many integrated tasks with difficult to measure progress. Technical points Hoteling is expensive, but solves many technical problems with file sharing and access as well as team communication issues.

A Model scope document, like a LOD requirement, or model progression matrix will help prepare the team, define the coordination issues that will need to be addressed, and plan the technical solutions required in Location 2.
10

Location 2 (Where are your Files?)

Understand how the files will be transferred and/or shared. How the whole projects data must be assembled from information from multiple locations
Implications If team members must collaborate between multiple locations on Revit files, you have to decide where the files will reside relative to the team members. Single Shared Location Ideally everyone shares a single file store (lets try to go back to forgetting about location!). There are some viable options for this strategy, but they too have drawbacks. Cloud Autodesk Cloud has potential to allow this kind of collaboration. Questions remain as to how effective access controls and user administration will be for large teams. Security is always a concern when storing sensitive client data on someone elses servers subject to someone elses security and service agreements. Revit Server Revit server virtually in the same place, but not exactly. Always-On connections are still required between all locations for borrowing and auto sync streams. Theres no solution yet for crossing firewalls or providing project or file level access controls. VPN If you can legally and technically provide a VPN connection to your consultants, they can effectively map a drive to match your internal users, thereby allowing direct collaboration, but your bandwidth had better be HUGE. Remote Workstations You can also provide VPN access and remote desktops. If the VPN hurdle can be overcome, then consultants can locate their own equipment and licenses, or you can provide equipment and maybe licenses so that consultants work in remote desktop on a local copy of Revit. This is less bandwidth intensive. Citrix Solve the Bandwidth problem inherent in the VPN solution by having the software literally hosted from the same server. Users remote into a server where the software runs and the files are all local. Great concept, as long as you can get past providing your consultants and team members with VPN connections (are their security protocols sufficient?) The EULA for Autodesk 2012 products allows for this use, but you still need licenses on the server. Are you providing your consultants with free licenses, or are they willing to pay? The other drawback here is the cost of a server, cluster or blade server of sufficient power to support the simultaneous use of Revit and/or other hardware-intensive applications by the entire project team. 11

Local Working files, Duplicated reference files We can try and work just like with AutoCAD. We will use relative paths in links, and local copies of other files for reference. The question here is how much time will you be willing to spend downloading 300 MB files, opening (Detach from Central) and placing in your local project directory. You can add scripting to accomplish much of this, but its still a management issue, especially enforcing the relative paths, and uniform directory structure at each location that will be required for this to work smoothly. Buzzsaw, SharePoint/FTP/etc., Copy/synchronization scripts All of these techniques share the same drawback; You have to balance the bandwidth/time required to download the files, the management required to remove UNC paths from workshared Revit files, and consider how long youre willing to go between updates. Its possible on a large project to be talking about a full-time employee doing uploads, downloads, detachments and updates. Local Working Files, Remote reference files This goes back to the single location idea kind of. We could let everyone work locally, and reference everyone elses files where they sit. WAN/VPN connections This works best behind a firewall (within a single, multi-location company). With multiple companies, a technical solution that allows direct file access between networks must be developed. This is generally either a separate secure WAN for the project, or a VPN that can be shared by multiple organizations. Tradeoffs File location decisions mean finding a balance between File Control/Management o User Access Control o File locking, history o Naming, Directory structures, links File Accessibility, currency o Age of reference files o Availability of new files System/infrastructure cost o Servers (Citrix, Revit Server) o Bandwidth (all) o WAN Acceleration (WAN, Revit Server) o Services (collaboration websites)
12

Rating
Replication
Collaboration WAN websites OK 3 YES Better 2 OK 2 NO OK
Revit Server Better 4 NO OK
Citrix
Complexity and User Interaction Works Outside Firewall Minimal Infrastructure Requirements (cost)
Worst 1 NO Best 1
Best 5 YES Worst, but 5
Operational Speed
Best (all Local)
Best (all Local)
Worst (?) 5
Better 2
Best (all Local, as far as the software knows) Best Best
Management Required Reliability & Fault Tolerance Scalability Security and tracking on models
Manual Bad
Manual OK
Little Bad
Better Better
Bad None
OK Best
Bad N/A Nice userbased History avail. No controls.
Best None on models, (VPNdependent for user control)
About Revit Server Revit Server is an Autodesk application provided as a subscription advantage tool (free with subscription). Revit server is a connector between Revit models, not a modeling application. Think of Revit server as a communications manager for projects and models that are worked on by teams with members distributed between multiple locations.
13

What it does Revit server is designed to take a Revit project that uses worksharing and make it practical for "Change before you have to." users in multiple locations to share the same central file. It does this by streaming information - Jack Welch to a local central file cache on a LOCAL REVIT SERVER in each office from a single central file located on the CENTRAL REVIT SERVER. This allows users in each office to work as-if the central file was located in their office, and still stay in sync with team members working on the same data in other locations. Why we use it We use Revit server when we have multiple users in multiple locations. It virtually eliminates the lag time experienced when borrowing elements or Synchronizing with the Central file (SWC/STC/saving to central) over the WAN (Wide Area Network between offices) and provides an extra layer of protection against file corruption that can happen when people save to central over a slow WAN connection.
Without Revit Server This is what Happens. Any delays in the WAN connection create longer delays for users borrowing elements or synchronizing to central. STC times can increase more than 10-fold when someone is trying to save over a slow WAN connection and others attempt to save as well.
We attempt to fix this by having users remote into a local desktop using Remote Desktop Connection. This is an effective way to reduce lag and eliminate the problems of working over the WAN, however it requires extra hardware at the host location for users to remote into. Revit 2012 now allows for virtualization in the EULA, but there are still technical problems 14

with Revit working in multiple sessions on the same hardware. With Revit Server, the server provides a replica of the file on each
LAN and mediates the stream of information between all LAN locations and the Central server over the WAN.
15

Performance Improvements Revit Server provides definite and noticeable performance improvements over working directly through the WAN. The following test speeds were collected during Business hours, on a 69.5 MB Revit model. The model was workset enabled. The Open command was to Open the Central file and create a new local. The Synchronize to Central command was triggered after copying all building elements visible in the default 3D view 300 feet to the south, and was run with the option of saving a local copy before and after, as is standard for users doing production work. For medium and large projects, where synchronizing files from the LAN can take 5-6 minutes and more, and users must synchronize a MINIMUM of twice a day, Revit server can save a medium-large project an HOUR per user per day!
6 minute LAN STC *6.0 = 36 Minute WAN STC 6 minute LAN STC *1.45 = 8.7 minute RS STC = 27.6 Minutes Saved Per STC
File/Open type (Fastest to Slowest)
File Open
Synchronize with Central Time Savings N/A Elapsed Time 0:18.9 0:22.5 1.0 Time Savings N/A 1:52.4 (83%)
Elapsed Time From Local Disk (C:\) From LAN 0:23.5 0:29.3 1.0
N/A
From Revit Server
0:48.8 1.67
0:04.0
0:32.6 1.45 1:42.3 (76%) 2:14.9 6.00 0:0 (baseline) N/A
From WAN, with Riverbed Acceleration (cached) From Revit Server, First Load in Location From WAN, no acceleration (1st load, not Cached)
0:52.8 1.80
0.0 (baseline) +32.4 (157%) N/A
1:28.7
0:56.3
N/A
What Revit Server doesnt do Revit Server doesnt work with files that arent workshared (workset-enabled central files). Revit Server doesnt automate Save-to-Central or Sync-With-Central operations. Revit Server doesnt change the fact that you need borrow permissions on elements, and sometimes need to sync with central when others need an element. It also wont 16

increase the upper limit of how many people can effectively work simultaneously in a single file. This is still around 6. Revit Server doesnt allow for project-specific access permissions. There is one list of projects on the server. All users see all projects. A network of Revit servers can only have one Central server, and local machines can only connect to 1 local server.
When to use Revit Server Revit Server should NOT be used for every Revit project. Only certain projects are right for Revit Server. These are: Projects where many team members from offices other than the primary office will work in Revit long term. Projects where multiple users need to work on the same Revit file from multiple locations simultaneously. Projects with other special communication needs across multiple locations.
Note that Revit server is SLOWER than working together over the LAN in the same office. Consider how many people will be remote versus local and whether the savings for remote users will outweigh the slowdown for local users. Also consider the history of the project for file corruption. Revit Server eliminates (in testing so far) central file corruption caused by saving to central across the WAN. Once a project has been moved to Revit Server, Everyone must use Revit server; it is no longer an option to have 1 team member work across the WAN. If they dont have a Revit server in their local office, they must connect to one across the WAN. This is the slowest possible option for working on a Revit file. Organizational Points What mechanisms allow files to be accessed by a distributed team? Controlling Access will be important who has permission and how is it enforced? Model communication, borrowing, updating, and linking. Security Concerns Managing versions Technical points UNC and Mapped Paths, Bandwidth Saving to Central Firewalls and VPNs Hardware Requirements
17

Location 3 (Where is the Data?)

Creating data that is compatible across multiple files from multiple sources, and with the end deliverable can be a challenge.
Understand how data must be organized within individual files. Planning Shared Parameters, Titleblocks, and schedule formats Graphic Standards still happen. Data fields, Model contents, database connections Defining the deliverable, Enforcing Compliance.
Implications Architectural models like to be contiguous for a building, Shell and Core divisions work most often. MEP models like to be contiguous per system.. so that connections can be easily maintained. Structural models like to be contiguous to expansion/seismic joints, so that loads are analyzed without skyhooks. Workstations require nearly 20X the TOTAL LOADED FILE SIZE in RAM. This means that the project must be divided into sections small enough to fit within that threshold, while allowing the user to (at least sometimes) load all of the other models they must be coordinating with. Sheets are easiest to manage when they reside in the same file that the model content theyre displaying is located. Some content must be aggregated from multiple, or all linked files. Users need to find the data they have to develop and maintain. External Keynote files provide a data management solution, and a multi-lingual project solution. Tradeoffs More models are harder to manage, but smaller segments run faster Project dividing lines need to line-up between disciplines and consultants, or its difficult to load all of 1 area of the building. Sheets are managed best in multiple files, but printing becomes time consuming. Its nice when everyone can use their best-native applications for documentation, but its easy to underestimate the budget and schedule impact of file translation for large projects. Organizational Points Early definition of deliverables is a huge help in planning the location for all of the project data. Clients need to be prompted to consider and define their database delivery needs early, so that consistent data field definitions can be maintained for all parties. 18

Allowing a team member to backslide on their file format or data obligations has the potential to cost everyone more money. If a consultant suddenly requires DWG exports for base files because theyve failed to keep up in Revit, this can mean constant maintenance of hundreds of additional files from that point on. It is always cheaper and more efficient to capture data as its handled (during the design process) than to go back and integrate it later. Its not the same expense for the same deliverable if the decision is made late.
Technical Points Define Shared parameters early and distribute before a project starts. You can create the same shared parameter name, but unless you literally copy the text from one shared parameters file to another, the two parameters will have different GUIDs and never fall into the same column in a schedule. Add any analysis that is intended for the project to the early technical plan. Many modeling techniques affect the potential for analysis later. The team needs to know early if GBXML will be used for energy models, or if Structural analysis will be done in RAM or Robot.
19

Location 4 (Where is the Building?)

The importance of Shared Coordinates. o How to ensure everyone gets them right. o Shared Coordinates and DWGsNavisworksIFC other Platforms Experiences o 21 Miles away o IFC files Solutions o Establish and coordinate early in process o Locking down coordinates o Adding Coordinates to other files o The alignment cube o Site reference files
Implications Revit still has usable coordinate space issues Shared parameters are often misunderstood, easy to mess up, and can create dominoeffect problems in many linked files. Many file types dont support shared coordinates at all. Multi-unit dimensions arent available in all applications. Tradeoffs Visible topography in Revit for very large sites will require significant file translation. Organizational Points Pick a single Coordinate Master file that everyone will acquire coordinates from. Determine file types early so you can plan for other unit and location systems. Technical Points DWGs store shared coordinates as UCSs. Revit can read these, but graphics on linked 3D DWGs are poor. IFC translation improves graphics for 3D elements in Revit, but IFCs dont support shared coordinates or UCSs. DGN files dont support shared coordinates. NWC files will support shared coordinates, so long as everyone uses the correct export settings. If you dont have a 100% Revit project, its likely youll need to use the reference-cube workaround. Workarounds DWG Files Exported UCS
20

Other Formats Embedded link Reference Cube Understanding Shared Coordinates Concepts and Definitions Revit contains several Cartesian coordinate systems. Project and Shared Coordinates are visible and editable in Revit, The third is the built-in internal coordinates. Coordinate Systems Cartesian Coordinates All CAD systems use Cartesian coordinates to locate objects and describe shapes. Cartesian coordinates are just X-axis, Y-axis, and Z-axis distances from a theoretical "Origin" or center point. Coordinates are usually notated as (X,Y,Z) or (X,Y) when Z=0. Any object can be positioned in space by the distance and rotation from the Origin, (0,0,0) UCS (User Coordinate System) http://www.dailyautocad.com/2008/10/understanding-ucs-part-1.html User coordinate systems are set in AutoCAD when you wish to work on a grid that is in a different position relative to the origin, or at a different elevation or rotation. UCSs in AutoCAD are often used to document true and project north for drawings. Views can be oriented to a UCS to document a consistent alignment in multiple viewports. Shared Coordinates are just Revits version of the UCS tool for the management of alternate coordinate systems Revit Coordinates Internal Coordinates Like AutoCAD, Revit has a built-in default set of coordinates, similar to the World UCS. These are not visible or changeable in Revit 2009. The only real way to find them is to import a DWG marker with the world origin notated. Try ORIGIN.DWG in a plan or sheet view, Origin-to-origin to see the actual internal origin in Revit 2009. Revit files become error prone if the model is placed a large distance from 0,0, so it's wise NOT to try to match survey coordinates in plan. Draw buildings in a convenient location near the origin. Matching the survey can be done later with shared coordinates. Project Coordinates Project coordinates are those that Revit displays to the user. In Revit 2009 and older, the project coordinates are linked to the Internal coordinates, and can be treated as the same thing.
21

Shared Coordinates Shared coordinates are a separate coordinate system. You could think of these as Custom UCSs in AutoCAD terms. When file A is linked into File B in Revit, the position of file A within File B can be modified. The actual location of File A relative to B becomes a shared position. You can have more than 1 shared position for each file. By using shared coordinates, it is possible to link File B back into File A and have them line up, even though File A was moved in File B. Relative Positions Because Internal Coordinates never move, we never actually MOVE elements in a model to align them to linked files. Instead, we define Shared Coordinates that record the difference between the internal coordinates in 1 file and the internal coordinates in another.
Project Base Point(internal, Project Coordinates) Reads the difference between the model position where drawn, and it's shared position, or real-world location.
Project Survey Point (Shared Position)
22

Creating Revit Toposurfaces from Civil Data You have a civil document that includes contours that youd like to reference in Revit. Use the following steps to create a Revit file that has a toposurface that you can use in your project. 1. Update the BIM Plan recommended to create a separate file for the toposurface and associated slabs. This allows you to update the references and files from consultants without the overhead of the rest of the project, and to manage, update, and redefine links without having to deal with visibility issues in multiple 3D views. a. For large sites, break DWG reference files into multiple pieces that fit within Revits coordinate space, and create a separate RVT file for each. 2. Get Points or Contours 3. For Points a. Import directly into Revit b. Delete and recreate when updated. 4. For Contours a. if 2D, Convert to 3D b. If Proxy objects, export to standard objects. i. Open in Civil3D or AutoCAD with object enablers that make the contours visible (not just proxy boxes). ii. Export to AutoCAD c. Remove label text from contour layers i. Select all, filter to text and mtext, move to a new layer ii. d. Link DWG into Revit in 3D e. Create toposurface from linked file f. Update the reference and re-make the surface. 5. Managing sub regions and slabs Have a plan to handle re-creating subregions if you are forced to recreate the topography because of updates from the civil designer. For Contours Revit will create topography from contour drawings; you dont need to manually place points. Contours must be 3D polylines. Use the following steps to get there. Note: Its probably helpful to detach all xrefs, audit, purge and possibly wblock out the contents of a file from a consultant to strip away any invisible problems. If 2D Contours, Convert to 3D contours Join 2D lines into polylines. Set their elevation to be their literal height (535, for example)
23

If Proxy Objects, convert to plane Plines. Drawings created in Civil3D will often have the contours as smart autocad objects. If you open the file and the contours layer has just bounding boxes instead of the actual contours, these are proxy objects. Proxy objects are placeholders for active content that you dont have the tools installed for. You can tell that theyre proxy objects because of the name (AeccDbContour), and because they appear to connect with less intelligent lines and splines that are also contours. Usually, youll see this message when opening a DWG containnig Proxy objects you cannot read:
Identifying a proxy object
24

Open the file in AutoCAD Civil3D to see the contours: Isolate the contour layers. You may want to delete any extra junk like the disjoined lines visible in the bottom of this image:
Often, height labels are on the same layer as the contour, especially in Civil3D files. Quickly fix this by adding a new layer for contour labels, selecting all visible elements, using AutoCADs filter option in the properties palate to isolate all TEXT and/or MTEXT, and switch it to a different layer.
Then Export to DWG format. Civil3D drawings are DWG files, but they contain objects that cannot be read without the AecCivilBase Object Enabler. Revit doesnt support Proxy Objects and Object Enablers. By using Export, not Save As, you ensure the removal of these proxy objects.
25

If you dont have access to Civil3D, you will need the object enabler for the AutoCAD version you have. See http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=15131158&linkID=9240618 for 2011. You with this object enabler installed, you will be able to see and EXPLODE the topoline objects and achieve the same ends. When you open the file in plain AutoCAD, you will likely see this message. You can ignore the missing SHX file most times without concequence.
The file in AutoCAD will now show the contours. Some other layers have been thawed to provide other reference information from within Revit.
You may wish to check that no stray lines are left at 0 elevation. Switch to a side view with the view cube, select all of the 0 elevation items, and filter to the contour layers. Move any elements that should not be contours to another layer. Move contours to the correct Z elevation.
26

Link DWG into Revit in 3D Link the drawing into the default {3D} View.
You may still see warnings about ActiveX and proprietary components. As long as the topography shows up, its not too important that other Civil3D elements arent brought in.
It is also likely that you will see a warning about the file being a long distance from the origin. Revit will continue and use Center-To-Center instead of Origin to Origin in order to fit the file within the coordinate space accommodated by Revit. Once you have the topo lines visible in Revit, You can attempt to align them to the correct elevations.
27

Select the DWG file, and retype the elevation to match the desired height. Use Internal Coordinates, so that in your site file the project and shared coordinate systems are the same. With the correct elevation specified, Rotate the file so that True North and Project North match. Create toposurface from linked file With the topography in the correct location, create topography
Start the Toposurface Command from the Model Site panel of the Massing & Site Ribbon.
Choose to select Import Instance to generate the topography. You will need to select only the layers that have contours on them. (This is why we removed the text from these layers.)
28

When you click OK Revit will create the topography almost instantly.
Check it for major errors. If some lines were exploded flat you may see large dips in the surface. Check that only the correct elements were on the layers; you may need to return to AutoCAD to revise. Revit will place MANY points to help ensure that the topolines will match the DWG file. You can use the simplify Surface command to reduce the accuracy of the surface and thereby reduce the number of points, and size of the file. Consider simplifying the surface of extremely complex topography. You can reduce the complexity, then link the DWG into a site plan view in 2D and use the DWG to display the contours even if the toposurface doesnt exactly match. Just turn off the topography lines in visibility settings. Update the reference and re-make the surface. Reload the Updated DWG.
29

Then select the toposurface and Click Edit Surface.
Place 4 points well outside the boundaries of the toposurface, then delete the imported points. Select Create From Import again,
then delete the extra 4 points.
30

31

Managing sub regions and slabs Have a plan to handle re-creating subregions if you are forced to recreate the topography because of updates from the civil designer. Fixing Coordinates in Multi-Model Projects Issue: You have multiple files linked together (IE Arch, Struct, MEP, Site, etc.) and for some reason some or all files are not staying aligned. Applies to:
Revit 2008, 2009, 2010, and 2011. File dialogs and menu descriptions are from Revit 2009.
Description: There is an issue with the Shared Coordinates in this project. Not all files have the same coordinate system published to them, and some linked files are not lining up in some of the models.
32

At least some of the projects files appear to not have the same alignment when linked into other models. Just because files appear to align in one model doesn't mean it's correct. See "Solution" below for the steps to correct everyone's shared coordinate settings. Cause: Usually this is because a model has been linked Center to Center (default value for Revit) instead of Origin to origin. Always link Origin to Origin. This can also happen if shared coordinates are in use, and someone moves a linked file accidentally. Avoid this by:
Always link Origin to origin. Link other models in BEFORE you start drawing PIN linked files so you don't drag them accidentally. Know that Moving a linked file in your file isn't a simple solution to an error in one of the items above.
Solution 1. Pick a Shared Coordinates Master file. If a Revit site file exists, use it. If not, pick another, or create a new empty file for Shared Coordinates, Save it to the project. Add a placeholder Object (some geometry that can be seen and aligned to in other files) and link all project files in, Origin to Origin. 2. Have your Project BIM Leader Edit the Shared Coordinates Master, Save a named location in this file (ProjectModelOrigin), delete any additional, unnecessary locations, and Publish coordinates to all the other files. If there are issues with borrowing the correct worksets to publish, then: a. Choose a person from the team for each file to check shared coordinates and update the files so that they align reliably for all other files. b. Have that person open their files and follow these steps: 1. choose a plan and/or section view, choose a linked file that aligns correctly with your file. Use detail lines to document it's position. 2. Activate the Manage Links dialog and make sure the links are all loaded, including the Shared Coordinates Master file. If the Shared Coordinates Master file is not loaded, link it (by shared coordinates, Named Location, called " ProjectModelOrigin". 3. Find the Shared Coordinates Master file in a view. "Project BIM Leader, provide a description of what it looks like. ex: "It's a 3D cube (generic model) just outside the building to the southwest." 4. Start the Tools>Shared Coordinates>Acquire Coordinates command, and select the geometry from the Shared Coordinates Master file. If you get the error message that coordinates are already coordinated, that's OK, proceed. 5. Go to the Settings>Manage Place an Locations tool. If ProjectModelOrigin does not say (current) next to it, select it and make it current. 6. Save to central and let your project BIM Leader know that your file is done. If your drawings no longer line up, don't panic. 7. When all files are located by the same shared coordinate system, the BIM leader can announce to everyone that it's time to proceed to step 8. 33

8. Reload all linked files 9. Select each linked Revit file in your model, click the Properties button. 10. Under Shared Location, make sure the button is labeled ProjectModelOrigin. If it does not, or says <Not Shared>, click the button and proceed to step 11, If it does already say "ProjectModelOrigin, then this link is correct. Click OK and proceed to step 12. 11. In this dialog, choose (1) Acquire the coordinates from this file. Then (2), Verify that the position being used is ProjectModelOrigin. If not then (3) change it to be ProjectModelOrigin, then (4) Reconcile locations. 12. Repeat steps 8-10 for each linked file. 13. check your view from step 1. If things don't line up, use Tools>Project Position/Orientation>Relocate this Project to move your file, vertically and horizontally until the reference lines you drew line back up with the linked files. 14. Turn the visibility of the Shared Coordinates Master file back off as needed. 15. Save to Central c. This should ensure that everyone who thinks they are lining up with the model is actually lining up the same way in everyone else's model. It will also ensure that files exported for NavisWorks clash detection align correctly. 3. Sometimes model managers will create the coordinates file, check out the Project Information workset, and not check it back in. Theoretically, this will prevent users from inadvertently altering the shared coordinate locations, since they'll be prompted to request permission before they're allowed to make any changes. An Illustrated list of steps follows: 1. choose a plan and/or section view, choose a linked file that aligns correctly with your file. Use detail lines to document it's position. 2. Activate the Manage Links dialog and make sure the links are all loaded, including the Shared Coordinates Master file. If the Shared Coordinates Master file is not loaded, link it (by shared coordinates, Named Location, called " ProjectModelOrigin". 3. Find the Shared Coordinates Master file in a view. "Project BIM Leader, provide a description of what it looks like. ex: "It's a 3D cube (generic model) just outside the building to the southwest."
(this is an example, refer to your specific project team for what the Shared Coordinates Master file looks like.
34

4. Start the Tools>Shared Coordinates>Acquire Coordinates command, and select the geometry from the Shared Coordinates Master file. If you get the error message that coordinates are already coordinated, that's OK, proceed.
5. Go to the Settings>Manage Place an Locations tool. If ProjectModelOrigin does not say (current) next to it(1), select it and make it current (2).
35

6. Save to central and let your project BIM Leader know that your file is done. If your drawings no longer line up, don't panic. 7. When all files are located by the same shared coordinate system, the BIM leader can announce to everyone that it's time to proceed to step 8. 8. Reload all linked files 9. Select each linked Revit file in your model, click the Properties button.
10. Under Shared Location, make sure the button is labeled ProjectModelOrigin. If it does not, or says <Not Shared>, click the button and proceed to step 11, If it does already say "ProjectModelOrigin, then this link is correct. Click OK and proceed to step 12.
36

11. In this dialog, choose (1) Acquire the coordinates from this file. Then (2), Verify that the position being used is ProjectModelOrigin. If not then (3) change it to be ProjectModelOrigin, then (4) Reconcile locations.
37

12. Repeat steps 8-10 for each linked file. 13. check your view from step 1. If things don't line up, use Tools>Project Position/Orientation>Relocate this Project to move your file, vertically and horizontally until the reference lines you drew line back up with the linked files.
38

14. Turn the visibility of the Shared Coordinates Master file back off as needed. 15. Save to Central
39

Conclusion, Location (Where is your plan?)

A Project Planning Checklist 1. Educate the client a. Data requirements 2. Prepare the team a. Deliverables List b. File sharing strategy c. Write a BIM Execution Plan Keep a copy in the project directory and update it throughout the project. Tell everyone about it. d. Kick off the project with a BIM planning meeting. Document items discussed in the technical plan (BIM Execution Plan, or BEP) i. Review the BEP ii. Review the LOD, Model Progression matrix in detail. iii. Confirm with group: Model Names, Workset Names, Import/Export/upload/Download schedules. iv. Discuss Efficiency Strategies and Ideas 1. Linking/Combining files, Hosting/not hosting MEP equipment 2. Groups, Similarities, Analysis procedures v. Review with the group specific model goals and output/analysis that will be needed from the BEP. vi. Discuss Staff experience. Is there anything you dont know how to do? When will you need training on this topic? vii. Communicate with your office BIM Leader about staff, training, and software/computer needs. e. Communicate with the team often. A 15-minute standing meeting every week is appropriate. This is enough time to allow each user to state the following i. What theyre working on this week ii. What Information they need from Others iii. Other changes or project impact they expect. iv. If theyre ahead, behind, or on schedule/budget. 3. Plan the model files a. BIM Execution Plan b. Model Progression Matrix 4. Plan analysis and clash detection 5. Utilize the model Data well.
40

Opening Questions to pose with the Client & Constructor at project kickoff 1. Client: What information requirements do Pre-Contract if possible! you have for your facilities? What end goals will you have for building The items discussed in the conversation outlined below documentation data on the day of occupancy? Do you have an FM System? & left can have an effect on the desired contractual arrangement, fee schedule, and other items best What kind is it, and how do you use it? broached prior to making legal arrangements. What is the ideal delivery method for design, construction, and operations information? a. Discuss COBIE, Databases, FM Translation, FM System hosting 2. Client & Constructor: How will the model be used during construction? Will the constructor manage progress, coordinate drawings, document completion, and/or run clash detection using the models? If so, what type of data will be in the model? Which elements could be reused from the design model and which will be re-created by designassist contractors, the CM, or be replaced by shop drawings? 3. Client & Constructor: Discuss the model types and Terms: a. MEA, Model Element Author Who draws what which consultants, contractors, and clients will add information to the model? b. LOD (Level Of Detail) How realistic and literal will the model be? What kinds of information will it contain? c. Contract Document What will be the instrument of service? Drawings (traditional management) or the model (IPD, or special contractual arrangements)? d. Design Intent Model Used as, or to create contract documents e. Construction Model Could be an evolution of the design model, or a new model altogether Elements broken down differently by trade, installation, etc. (includes Means & Methods). This model is usually more specific and detailed. f. Federated Model (An aggregation of multiple models to construct the big picture; Usually done in NavisWorks.) g. 3D Shop Drawings, Fabrication Model ( (LOD 400) used for manufacturing and pre-assembling units, usually done by subcontractor as a shop drawing, but can be integrated into a federated model for construction coordination.) h. As-Built vs Record Set model (As-Built model is expensive, changes LOD to 500, must be done by or with the CM. Record Set model doesnt change the LOD or MEA, but updates drawings to reflect change orders, etc. as in a traditional record set.) i. Model-based cost estimation What is and is not in the design model. j. Clash Detection, clash management: What is a clash free model? How is this achieved? What kind of time investment is required to maintain clash detection? What are the potential paybacks? 4. Client & Constructor: Discuss the concept of IPD: Contractual changes, Performance goals and reserves, Zero Change Order processes. 5. Client & Constructor: When does Designer/Constructor interaction in the model begin? Is the constructor willing to work with the AE during design on model integrity and CA readiness? What kind of contract will be guiding the design and construction phases? Will collaboration be a possibility? Will the collaborating partners be paid for results and/or effort on collaboration pre and/or post-bid (IPD?) 41

6. Client & Constructor: Introduce the effort curve for BIM vs. traditional delivery projects. Discuss billing cycles and deliverables.
7. Client & Constructor: Introduce the LOD/R Matrix; discuss data delivery fields, Levels of Detail, and MEA/Ownership/Responsibility transfer for models. 8. Client & Constructor: Schedule a full BIM Planning session to begin prior to contract arrangement, if possible. List goals: a. Identify BIM Management team Members from each party (contractor, client, designer, consultants) b. Create a full LOD/R Matrix document for project delivery goals c. Write a BIM Execution Plan (BEP, URS has a template.) d. Arrange regular review meetings to complete and maintain the procedures, goals, and status of the LOD/R and BEP, this will evolve into a clash management and model review meeting, and then into construction progress meetings, and finally into BIM/FM Delivery meetings (if required.) BIM Execution Plan Requirements Reference; Penn State Model Template, IU Plan, Consensus Docs 300, AIA E202
42

LF5038 - Location, Location, Location-Handout

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LF5038 - Location, Location, Location-Handout

Uploaded by

Copyright:

Available Formats

Location, Location, Location: 50 Models, 50 Contributors, 20 Companies, 5 Buildings, and 1 Site

Jon Anunson URS Corporation Marla Caserta URS Corporation

About the Speakers

Marla Caserta, AIA, Cleveland OH BIM Leader, URS Corporation.

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Location 1 (Where is your team?)

Location 2 (Where are your Files?)

Location 3 (Where is the Data?)

Location 4 (Where is the Building?)

0:50 0:55 0:00

0:05 0:05 1:00

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Location 1 (Where is your team?)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Location 2 (Where are your Files?)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Collaboration WAN websites OK 3 YES Better 2 OK 2 NO OK

Revit Server Better 4 NO OK

Best 5 YES Worst, but 5

Best (all Local)

Best (all Local)

Best (all Local, as far as the software knows) Best Best

Bad N/A Nice userbased History avail. No controls.

Best None on models, (VPNdependent for user control)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

File/Open type (Fastest to Slowest)

From Revit Server

0:32.6 1.45 1:42.3 (76%) 2:14.9 6.00 0:0 (baseline) N/A

0.0 (baseline) +32.4 (157%) N/A

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Location 3 (Where is the Data?)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Location 4 (Where is the Building?)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Project Survey Point (Shared Position)

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Identifying a proxy object

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

Then select the toposurface and Click Edit Surface.

then delete the extra 4 points.

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location:

LF5038 Location, Location, Location, Location: