Transcript
AutoCAD Civil 3D 2008
Best Practices with Pipe Network Parts Catalogs
July 2007
©
2007 Autodesk, Inc. All Rights Reserved. Except as otherwise permitted by Autodesk, Inc., this publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose. Certain materials included in this publication are reprinted with the permission of the copyright holder.
Trademarks The following are registered trademarks or trademarks of Autodesk, Inc., in the USA and other countries: 3DEC (design/logo), 3December, 3December.com, 3ds Max, ActiveShapes, Actrix, ADI, Alias, Alias (swirl design/logo), AliasStudio, Alias|Wavefront (design/logo), ATC, AUGI, AutoCAD, AutoCAD Learning Assistance, AutoCAD LT, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, Autodesk, Autodesk Envision, Autodesk Insight, Autodesk Intent, Autodesk Inventor, Autodesk Map, Autodesk MapGuide, Autodesk Streamline, AutoLISP, AutoSnap, AutoSketch, AutoTrack, Backdraft, Built with ObjectARX (logo), Burn, Buzzsaw, CAiCE, Can You Imagine, Character Studio, Cinestream, Civil 3D, Cleaner, Cleaner Central, ClearScale, Colour Warper, Combustion, Communication Specification, Constructware, Content Explorer, Create>what's>Next> (design/logo), Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignKids, DesignProf, DesignServer, DesignStudio, Design|Studio (design/logo), Design Your World, Design Your World (design/logo), DWF, DWG, DWG (logo), DWG TrueConvert, DWG TrueView, DXF, EditDV, Education by Design, Extending the Design Team, FBX, Filmbox, FMDesktop, Freewheel, GDX Driver, Gmax, Heads-up Design, Heidi, HOOPS, HumanIK, i-drop, iMOUT, Incinerator, IntroDV, Kaydara, Kaydara (design/logo), LocationLogic, Lustre, Maya, Mechanical Desktop, MotionBuilder, ObjectARX, ObjectDBX, Open Reality, PolarSnap, PortfolioWall, Powered with Autodesk Technology, Productstream, ProjectPoint, Reactor, RealDWG, Real-time Roto, Render Queue, Revit, Showcase, SketchBook, StudioTools, Topobase, Toxik, Visual, Visual Bridge, Visual Construction, Visual Drainage, Visual Hydro, Visual Landscape, Visual Roads, Visual Survey, Visual Syllabus, Visual Toolbox, Visual Tugboat, Visual LISP, Voice Reality, Volo, and Wiretap. The following are registered trademarks or trademarks of Autodesk Canada Co. in the USA and/or Canada and other countries: Backburner, Discreet, Fire, Flame, Flint, Frost, Inferno, Multi-Master Editing, River, Smoke, Sparks, Stone, Wire. All other brand names, product names or trademarks belong to their respective holders.
Disclaimer THIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AUTODESK, INC. "AS IS." AUTODESK, INC. DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE REGARDING THESE MATERIALS. Published By: Autodesk, Inc. 111 Mclnnis Parkway San Rafael, CA 94903, USA
1 2 3 4 5 6 7 8 9 10
Contents
Chapter 1
Best Practices with Pipe Network Parts Catalogs . . . . . . . . . 1 How the Parts Catalog Works . . . . . . . . . . . . Parts Catalog Management Practices . . . . . . . . Problematic Scenarios . . . . . . . . . . . . . . . Local Catalogs and a New Part . . . . . . . . Local Catalogs and a Modified Part . . . . . Networked Catalogs on Different Networks . Drawing Shared Between Two Companies . . Conclusion . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
.2 .3 .4 .4 .4 .5 .5 .6
iii
iv
1
Best Practices with Pipe Network Parts Catalogs
The pipe network parts catalog is a great feature of AutoCAD®
In this chapter
Civil 3D® software, but there are definitely some rules to
■
How the Parts Catalog Works
follow for best results. This document explains best practices
■
Parts Catalog Management Practices
■
Problematic Scenarios
■
Conclusion
for using the parts catalog, and describes particular work scenarios that can cause problems.
1
How the Parts Catalog Works When pipe networks are created or edited, AutoCAD Civil 3D references the parts catalog for information about each part (pipe or structure). You can use the Part Builder utility to edit the data for any part, and to expand the catalog by creating additional custom parts. As shown in the following figure, each part is defined by three files with the same root name but different extensions:
Catalog files for two types of circular pipe
If you use Part Builder to modify a part, you will probably change the XML file, as it contains the detailed dimensions and calculations. Changes to the DWG™ and BMP files are possible, but not essential in every case. AutoCAD Civil 3D installs the default pipe network parts catalog at C:\Documents and Settings\All Users\Application Data\Autodesk\C3D 2008\enu\Pipes Catalog. You can point your drawing to a different catalog by clicking Pipes menu ➤ Set Pipes Network Catalog, and then changing settings in the following dialog box:
Dialog box for specifying the pipe network catalogs
In a multi-user work environment with multiple parts catalogs, it is very easy to create unwanted changes in drawings if your parts catalogs do not have consistent contents and standard locations. Unwanted changes can occur because each drawing references the parts catalog at the location specified on
2 | Chapter 1 Best Practices with Pipe Network Parts Catalogs
the computer on which it was created. If the drawing is opened on a different computer where it cannot find a catalog at the same location, it points to the default location, or whatever is defined on the second computer. Unwanted changes can occur to parts in the drawing if two conditions are met: the user of the second computer edits the pipe network with an operation that references the parts catalog, and the referenced part has specifications in the current catalog that differ from those in the original catalog. Under these conditions, the part specifications from the current catalog are applied to the part in the drawing. Operations that reference the catalog—and can introduce unwanted changes—include adding a part to the network or moving a part. Other operations, such as editing a label, do not reference the catalog.
Parts Catalog Management Practices To prevent errors in multi-user environments, use the following practices for managing pipe network part catalogs: ■
When changes to a parts catalog are expected, designate a single person (the ‘catalog manager’) to be responsible for making changes and maintaining the master parts catalog.
■
When the master catalog changes, the catalog manager distributes the updated catalog to all users or offices.
■
Users send all new or modified parts to the catalog manager for addition to the master catalog. Among the team, agree on a standard process for doing this. For example, users could send to the catalog manager an entire catalog folder, or just the affected files (DWG, XML, and BMP) for a single part.
■
If all users store their parts catalogs locally on their computers, the catalogs should be in the same location, preferably the default C: drive path used by AutoCAD Civil 3D.
■
If a number of users are on the same network, a single pipes catalog can be stored in a central network location. In this case, it is important for users to avoid changing the shared catalog, as they could interfere with the work of other users. Instead, the catalog manager should be responsible for making all changes and notifying the users.
■
When a new or modified part is required, always use Part Builder to make the edits. Manual edits to an .xml file can produce unwanted results.
Parts Catalog Management Practices | 3
■
When modifying a default part, save it with a new name so that it can be easily distinguished from the original part.
■
When sharing a drawing with another user, prevent unwanted part changes by setting the pipe network catalog to the same location, such as a shared network drive, or the default C: drive. If two separate catalogs are involved, verify that their contents are identical.
Problematic Scenarios The following sections describe scenarios that can cause unexpected changes in pipe network drawings. Solutions are provided that can prevent or recover from the problem outlined in each scenario.
Local Catalogs and a New Part 1 Users A and B are both using AutoCAD Civil 3D with the default pipe network catalog path (C:\Documents and Settings\All Users\Application Data\Autodesk\C3D 2008\enu\Pipes Catalog\). 2 User A creates a new part and uses the part in Drawing 1. This new part exists only in the catalog on A’s computer. 3 User B edits Drawing 1 on his computer, and parts are referenced from the catalog. The new part created by user A is not available, so AutoCAD Civil 3D uses the closest part it can find. As a result, the part in Drawing 1 is changed. Solution: User A sends the new part to the catalog manager, who distributes it to User B and others, maintaining standard catalogs that contain identical parts.
Local Catalogs and a Modified Part 1 Users A and B are both using AutoCAD Civil 3D with the default pipe network catalog path (C:\Documents and Settings\All Users\Application Data\Autodesk\C3D 2008\enu\Pipes Catalog\).
4 | Chapter 1 Best Practices with Pipe Network Parts Catalogs
2 User A modifies an existing part X and uses the part in Drawing 1. The name of part X is not changed. 3 User B edits Drawing 1 on her computer, and parts are referenced from the catalog. Part X is found and used, but it is the default part X, not including the changes made by user A. Solution: User A saves the modified part with a different name, and sends the part to the catalog manager, who distributes it to User B and others. When modifying parts, users should change the part name to clearly identify the new part.
Networked Catalogs on Different Networks 1 User A is using AutoCAD Civil 3D with the pipe network catalog path set to a network location, such as N:\Autodesk\Civil3D 2008\Pipes Catalog\. 2 User A creates a new part and uses the part in Drawing 1. 3 User B in another office edits Drawing 1 on his computer, which has the pipe network catalog path set to a different network location, such as J:\Autodesk\Civil\Pipes Catalog\. Drawing 1 searches for the pipes catalog on the N: drive but does not find it. Therefore, AutoCAD Civil 3D substitutes the most similar part from the catalog on the J: drive and uses it instead. Solution: User A sends the new part to the catalog manager, who distributes it to User B and others to maintain consistent catalogs. Users of networked catalogs in different offices should agree to use the same drive letter and path for their parts catalogs. If this is done, drawings can be shared reliably and it is easier to maintain standard catalogs.
Drawing Shared Between Two Companies 1 Company A is using AutoCAD Civil 3D with the pipe network catalog either locally or on the network. Company A creates a new part or modifies an existing part. That part is used in a network in Drawing 1. The drawing is given to Company B.
Networked Catalogs on Different Networks | 5
2 Company B opens and edits the drawing, which points to the path where the catalog resided at Company A. If that was the default location, the drawing finds that path at Company B and looks there for the part. If the saved path was a network location that does not exist at Company B, AutoCAD Civil 3D looks in Company B’s default catalog location. If the part is a standard AutoCAD Civil 3D part with the name unchanged, it uses the one in Company B's catalog, regardless of whether it resembles the one Company A intended. If the part is new or a renamed standard AutoCAD Civil 3D part, the software looks in Company B’s catalog for the most similar part. Solution: Company A provides a copy of its parts catalog along with the drawing, asking Company B to reference this catalog, or update its current catalog to include the changes. Ideally the changes are clearly identified so that Company B can determine whether the updates from Company A would introduce any unwanted changes to other drawings.
Conclusion Pipe network parts catalogs are a convenient mechanism for standardizing the specifications of parts and structures across project drawings. But it is important for all users to understand how AutoCAD Civil 3D consults these catalogs and updates drawings during the editing process. In any environment where multiple users are sharing drawings, they should follow a standard procedure for maintaining and distributing the parts catalog to avoid unwanted part changes in drawings. All parts catalogs in use among a design team should be identical, and they should be stored in consistent locations. If this is done, the parts catalogs are referenced in a predictable way, and it is easier to find and update them when required.
6 | Chapter 1 Best Practices with Pipe Network Parts Catalogs
