Design Process

Keep track of the design process

Building and product designers know first-hand that it takes multiple versions of the same design, multiple iterations on those versions based on stakeholder feedback, and final changes leading to owner approval. Furthermore, each of these design versions may contain a number of comments, markups, and redlines.This entire process can be long, disjointed, and complicated, leaving behind a haphazard trail of file versions on multiple devices that become very difficult to track.

A360 provides a complete history of the design process including version tracking, markup history, and comment records. Track, and keep track of, all project design files without changing the way an organization or team works.

Versions

Versions are created when a user uploads a file with the same filename as a previously uploaded file. These versions are accessible when any team member or contributor opens a file from the project folder. At the top of the immersive viewer screen users can see a drop-down menu of all earlier versions and access them with just a click. Historical version tracking is built-in and doesn’t require a change in the way you upload files; in fact, this method of versioning eliminates the cumbersome file nomenclature associated with manual file versioning.

A360 Versioning Design Process

Comments

Comments on design files are great for getting feedback. The commenter can tether the comment to an exact view or an exact point on the drawing or model so the designer knows exactly what he/she is referencing.

Comments are also tied to versions, so when a user views an older version, the user will only see the comments made on that version. This makes it easy to track the changes that were made based on direct feedback, and the order of those changes.

A360 Comment Feed

Markups

Writing or drawing directly on a drawing or model is another way to give feedback in an easily trackable way. As is the case with comments, markups are also made on only one version at a time, which means that users can see in the next version if their feedback was taken into account.

All of this feedback and version tracking leads to a wealth of historical data. Keeping track of the design process gives everyone on the project team a clear sense of progress, insight into their feedback results, and a better understanding of opportunities for process improvement.

 

A360 Markups Design Process

If you have questions about tracking the design process in A360, join us in the forums.

Elizabeth Katzki

Elizabeth Katzki is a Marketing Specialist for A360.

More Posts

4 replies
  1. Ethan Lipman
    Ethan Lipman says:

    Great work! Looks like AutoDesk is making great strides in their transition to more cloud based tools. I use AutoCAD on Mac and PC. How much of this A360 comment and version control works identically from Mac same as PC? Upload to A360 from either and all comments are stored in the cloud? I just submitted this idea to idea station – https://twitter.com/etlipman/status/720345604577046528 – hoping to see tighter and tighter A360 integration from both PC AND Mac platforms. Thanks! -Ethan

    Reply
  2. Marcin
    Marcin says:

    What will happen when you add the comments to the model and in 2 weeks time as progress design model will be replaced with the new one, if those comments will stay on the new model or will be lost ?

    Reply
    • Elizabeth Katzki
      Elizabeth Katzki says:

      Comments won’t be removed unless directly deleted by a user, so comments on previous versions will remain. They are, however, tied to the version of the file that you made the comment on. When you scroll through comments on a file, you will see that they are organized by version. You can also see comments by version by rolling back to previous file versions in the version dropdown menu.

      If you have further questions, please don’t hesitate to reach out to our A360 experts in the forums.

      Reply

Trackbacks & Pingbacks

  1. […] post Keep track of the design process appeared first on A360 […]

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>