VIDEO
HIGHLIGHT
Log InSign up
ECB GV11 SESION 16
SummaryTranscriptChat

ECB GV11 SESION 16

Class Overview and Initial Setup

Introduction and Class Objectives

  • The instructor greets the class, expressing hope that everyone is well and inquiring about their ability to request a trial version of Revit.
  • Emphasizes that today's session will be practical, encouraging students to share their experiences with opening the group project in Revit.

Group Project Confirmation

  • The instructor stresses the importance of resolving issues immediately rather than waiting for future classes, highlighting that only four students have confirmed access so far.
  • Discusses how different groups may be using various versions of Revit, which affects visibility in the software.

Trial Version Issues and Team Coordination

Importance of Participation

  • The instructor urges those who haven't requested the trial version to do so promptly, as multiple team members need access to maximize platform benefits.
  • Requests confirmation from students regarding their ability to see their respective teams in Revit.

Attendance Check

  • The instructor begins taking attendance based on student responses (thumbs up or emojis), while also addressing individual issues related to software access.

Group Dynamics and Software Functionality

Identifying Active Groups

  • Acknowledges which groups are operational within Revit, noting that some groups are more active than others.
  • Confirms which version of Revit each group is using to ensure compatibility during collaboration.

Practical Application Session

  • Informs students about practicing model coordination and publication processes during this session, emphasizing hands-on experience with architecture and installations projects.

Navigating Revit: Hands-On Practice

Project Structure Understanding

  • Explains the project's division into architecture and installations components, stressing the need for teams to simulate interactions between these areas.

Opening Projects in Revit

  • Guides students through accessing shared models within Revit while confirming successful logins from all groups involved.

Troubleshooting and Collaboration

Addressing Technical Issues

  • Encourages students experiencing difficulties with program openings or file access to communicate openly for assistance.

Collaborative Learning Environment

  • Highlights that errors encountered during practice sessions are valuable learning opportunities; encourages sharing screens for collaborative troubleshooting among peers.

Accessing and Managing Project Files

Initial Access Issues

  • Discussion on updating or navigating to another folder to refresh access to recent files. The speaker mentions that they have granted more access and asks for confirmation if the changes appear.
  • Acknowledgment of a participant named Roberto, who is asked about their group affiliation.

Troubleshooting Steps

  • Request for Roberto to perform a specific action mentioned earlier by Ron, indicating collaborative troubleshooting.
  • Confirmation from Ron regarding visibility of project files, with speculation that internet speed may be affecting file loading times.

File Management Techniques

  • Emphasis on analyzing access permissions while working through the process. The speaker notes personal time constraints and requests group identification.
  • Confirmation that updates were successful, with discussions about previous loading issues due to slow internet connections.

Creating User-Specific Views

Setting Up 3D Views

  • Introduction of creating a 3D view in the browser interface, highlighting its importance for user navigation.
  • Instructions on color coding views based on discipline and status, stressing uniformity among users while maintaining individual identifiers.

Importance of Personalized Workspaces

  • Explanation of how personalized views are essential for effective modeling and documentation within the project environment.
  • Encouragement for participants to notify when they complete setting up their personalized views.

Collaborative Architecture Work

Group Collaboration Dynamics

  • Mention of collaboration in architecture work with an emphasis on shared responsibilities among team members.
  • Recognition that not all folders may appear immediately due to system functions; encouragement towards patience as everyone learns together.

Synchronization Process

  • Highlighting the necessity of having a functional workspace where comments and annotations can be preserved without loss during synchronization processes.

Synchronization Challenges

Real-Time Collaboration Issues

  • Participants are instructed on how to synchronize their models effectively while acknowledging potential challenges in real-time collaboration.
  • Description of visual indicators during synchronization processes, such as loading symbols representing active syncing by other users.

Final Synchronization Steps

  • Clarification that after initial synchronization, users may need additional sync attempts to ensure visibility across different user perspectives.

Project Organization and Collaboration Techniques

Steps for Project Setup

  • The first step in organizing a project is to create a project template. This involves duplicating an existing plan and adding your initials to it for identification.
  • When duplicating views, it's essential to rename them appropriately by removing the word "copy" and appending your initials. This helps maintain clarity in documentation.
  • Ensure that the view properties are adjusted correctly; specifically, remove any templates that may restrict changes to the discipline settings.
  • If you encounter issues with templates preventing modifications, remember to set the template option to 'none' before proceeding with adjustments.
  • Proper synchronization is crucial; if problems arise during this process, they may not be due to individual actions but rather technical issues like internet connectivity.

Managing Subprojects

  • To create a new subproject, use your name as a placeholder for practice purposes. In real scenarios, more descriptive names should be used for clarity.
  • After creating a subproject, ensure it reflects accurately in the main project overview by synchronizing it properly.
  • Understanding permissions is vital; when creating subprojects, make sure they are editable only by their respective owners unless sharing is intended.
  • Always confirm whether you want your newly created subproject active. This ensures that all team members can see and access it as needed.
  • Be cautious about enabling options that allow others to edit your work; maintaining ownership of your contributions is important until you're ready to share them broadly.

Team Coordination and Visualization

  • Synchronization plays a key role in ensuring everyone on the team has access to updated information regarding subprojects and overall progress.
  • Once synchronized, check that all team members can view the newly added subprojects within their projects effectively.
  • Teams must establish clear communication regarding object classification within 3D views; this includes agreeing on color coding and detail levels for better organization.
  • Utilize available tools such as property filters or categorization options within software platforms to streamline collaboration efforts among team members.
  • Assign specific tasks or objects (like columns or profiles) among team members based on expertise or preference for efficient workflow management.

Understanding Subprojects in Revit

Setting Up Subprojects

  • The speaker discusses the importance of defining subprojects and how to select various pillars for a project, emphasizing the need for clarity in properties.
  • A specific example is given where the subproject is named after an individual (Juan Francisco Ángel), which affects object color coding based on ownership views.

Object Ownership and Synchronization

  • The process of analyzing subprojects occurs in the background within Revit, allowing users to see graphical changes when objects are assigned to different owners.
  • Emphasis is placed on ensuring that each participant selects unique objects without duplication, fostering collaboration among team members.

Visual Changes and Collaboration

  • As Wilmer interacts with objects, visual feedback is provided through color changes indicating ownership; this helps track who has selected what.
  • Instructions are given to adjust view settings for better clarity, including setting colors by owner and disabling analytical views.

Understanding Ownership Dynamics

  • The speaker explains how ownership is tracked even without synchronization; it’s likened to a game where only one person can claim an object at a time.
  • Clarification on how unsynchronized actions still allow users to see who has claimed an object but may not reflect all recent changes accurately.

Synchronization Process

  • The necessity of synchronizing work is highlighted as crucial for maintaining accurate project updates and avoiding conflicts over object ownership.
  • Challenges related to synchronization timing are discussed, noting that network conditions can affect who sees updates first during collaborative efforts.

Final Steps in Collaboration

  • After synchronization, participants can verify their claims on objects; discrepancies may arise if others have synchronized before them.
  • The importance of reloading recent changes post-synchronization ensures everyone has access to the latest project state.

This structured approach provides insights into managing subprojects effectively within Revit while highlighting key collaborative practices essential for successful teamwork.

Synchronization and Object Management in Project Collaboration

Synchronization Process and Issues

  • The speaker discusses the synchronization of elements within a project, noting that changes made to certain columns do not reflect color changes despite being updated in the workspace.
  • Modifications can be made directly by selecting objects; however, synchronization is necessary for all elements to update correctly across the project.
  • The importance of using the correct synchronization option is highlighted, with a preference for "synchronize now" over other options to ensure immediate updates.
  • A participant mentions issues with version 2024.3.3, suggesting that earlier synchronization methods may have caused problems with element release.
  • The discussion includes testing different objects to see if they synchronize properly when moved between projects.

Object Ownership and Editing Rights

  • Participants are encouraged to share screens for better collaboration and understanding of object management within their projects.
  • It’s emphasized that when transferring objects between subprojects, users must confirm ownership status to avoid confusion during editing processes.
  • Clarification on how releasing a subproject affects object ownership is provided; participants need to understand their roles as lenders or borrowers of project components.
  • The conversation reflects on ensuring clarity among team members regarding editable statuses of projects and objects involved in collaborative work.
  • A summary of steps taken during the session indicates that some participants discovered new functionalities while others confirmed existing knowledge.

Best Practices for Collaboration

  • Leonardo raises a question about whether subprojects should be editable; it’s clarified that they should be marked as such for effective collaboration.
  • Emphasis is placed on maintaining clear naming conventions for subprojects to prevent confusion among team members regarding ownership and editing rights.
  • Participants are encouraged to request objects from one another, fostering an environment where sharing resources becomes standard practice within the project framework.
  • The speaker outlines potential challenges in collaboration due to overlapping edits but stresses the importance of organized communication among team members during these processes.
  • An example scenario illustrates how users can request permission before editing shared objects, reinforcing proper protocols in collaborative settings.

Working with Editable Objects in Zoom

Introduction to Editable Objects

  • The speaker discusses a project where everyone can participate, mentioning the need to research commands for using the arrow tool in Zoom.
  • A feature called "solo editables" is introduced, allowing users to select only their own objects within a shared environment.

Using the Solo Editables Feature

  • The speaker explains how selecting "solo editables" helps users manage their own objects without interference from others.
  • When attempting to interact with another person's object, a symbol appears indicating permission must be requested before editing.

Requesting Permissions for Object Editing

  • The analogy of borrowing a book is used to explain that when an object is borrowed, it remains under the original owner's name but is physically with someone else.
  • Users are encouraged to utilize the icon for requesting permissions instead of moving objects without consent, which could lead to confusion.

Managing Collaboration Settings

  • If the icon does not appear when trying to edit an object, users should check collaboration settings and enable controls for visibility.
  • Once enabled, users can see and request edits on objects they wish to work on collaboratively.

Handling Edit Requests and Ownership

  • Users can view requests they've sent and received regarding editing permissions. Accepting or denying these requests is crucial for maintaining order in collaborative projects.
  • The importance of accepting requests promptly is emphasized; otherwise, notifications may be missed.

Understanding Subprojects and Ownership Dynamics

  • The discussion shifts towards subprojects where multiple users might have ownership over different elements within a project.
  • It’s clarified that while one may own an object in a subproject, if it's lent out, it becomes temporarily owned by another user until returned.

Conclusion: Best Practices in Collaborative Environments

  • Users are reminded that managing editable objects requires clear communication about ownership and permissions among team members.
  • Emphasis on understanding who owns what within subprojects helps maintain clarity during collaborative efforts.

Understanding Ownership and Collaboration in Revit

Key Concepts of Ownership in Revit

  • The concept of ownership is crucial; users are considered owners of their elements but can lend them to others until requested back.
  • Revit introduces the idea of "state of belonging," which visually distinguishes between owned (green), borrowed (red), and unowned (white) elements, simplifying user interactions.
  • Before taking a break, the importance of ensuring all groups have successfully managed requests for lending and borrowing elements is emphasized.

Managing Projects and Subprojects

  • After the break, discussions will focus on managing recent projects, addressing graphical issues, and handling scenarios where team members go on vacation while others retain subprojects.
  • Configuration for publishing plans will be discussed, highlighting the need for agreement among team members to ensure smooth collaboration.

Synchronization and Information Management

  • A 15-minute pause is called before returning to confirm synchronization status among participants.
  • Participants are encouraged to utilize shared cloud resources effectively as more users join the project, enhancing collaborative efforts.

Specific Configurations in Revit

  • The function "reload latest" is explained as useful when no changes have been made for a while but new information needs to be received from the model.
  • Users are advised against liberating all personal elements at once; instead, they should selectively manage what they share through synchronization settings.

Visibility and Resource Management

  • Users can control visibility within subprojects by turning off views that do not pertain to them, thus conserving system resources during collaboration.
  • When opening models with editable options, users must decide whether to keep or release ownership over certain elements based on their current needs.

Efficient Model Opening Techniques

  • Users are reminded always to conserve ownership when prompted about editable items within their models.
  • The process of specifying which parts of a project to open allows for faster loading times by limiting unnecessary data retrieval from large projects.

Collaborative Model Management in Revit

Synchronization and File Access Issues

  • The speaker discusses the process of making a model editable, emphasizing the importance of synchronizing before opening it fully. Users are encouraged to test synchronization without making changes.
  • A reminder is given to wait for others to synchronize their files before proceeding, highlighting the need for coordination among team members.

Troubleshooting File Opening Problems

  • A participant expresses difficulty in opening a file in Revit, prompting a screen-sharing session to diagnose the issue.
  • The discussion reveals that users may need to request a trial version of "Bin Collabor Pro," as access links can vary by country.

Managing Project Ownership and Permissions

  • The conversation shifts to project ownership, particularly when team members go on vacation. The speaker explains how users can relinquish control over projects they own.
  • Ceding ownership is clarified; it only applies if another user has left without transferring their elements. This process requires caution due to potential risks involved.

Risks Associated with Ceding Ownership

  • The speaker outlines risks related to ceding ownership, such as losing access to model elements owned by other users who are not present.
  • Users can enter the cede option if they have previously retained elements but exited the file. This allows them or others to take over those elements under specific conditions.

Version History and Maintenance Practices

  • Regular maintenance practices are discussed, including using the "open and review" feature periodically when no one is working on the model.
  • Version history tracking is introduced as a way for users to monitor synchronization activities within the project, although its accuracy may be questionable.

Clarifications on Ceding Process

  • A participant seeks clarification about modifying elements owned by absent users. It’s confirmed that modifications can occur if no one else is actively using those specific elements.
  • An example scenario illustrates how a user might assume ownership of an element after another user leaves, reinforcing understanding of this process.

This structured summary captures key discussions from the transcript regarding collaborative management in Revit while providing timestamps for easy reference.

Understanding Subprojects and Collaboration in Design

Managing Subprojects

  • The speaker discusses the visibility of active subprojects, emphasizing the importance of recognizing which subproject is currently being used for efficient workflow.
  • A hierarchy is introduced to help users quickly identify their active subproject, aiding in organization and clarity during design processes.

Ownership and Collaboration

  • The concept of ownership is explored; even if a user creates an object within another's subproject, they are considered a borrower rather than the owner.
  • It’s highlighted that contributions should be made in the appropriate subproject to maintain order and collaboration among team members.

Editing and Object Management

  • Users can make objects editable, allowing others to take ownership if they are left free. This encourages collaborative editing while maintaining accountability.
  • The speaker notes that understanding object ownership is crucial as it affects how team members interact with each other's work.

Project Structure and Visibility

  • Active subprojects are visually distinguished from others, helping users navigate between their own projects and those belonging to teammates effectively.
  • Clarification on non-editable items indicates that certain elements may not belong to the current user, reinforcing respect for project boundaries.

Collaborative Model Development Tasks

Teamwork in Model Creation

  • Emphasis on teamwork is reiterated; all members must contribute according to their designated roles without overlapping responsibilities unnecessarily.
  • Each member is required to create a unique plan with specific naming conventions that reflect individual contributions for better organization.

Plan Configuration Guidelines

  • Instructions are provided on setting up plans correctly, including adjusting scales and hiding unnecessary elements for clarity in presentations.
  • The necessity of having one plan per person ensures focused contributions while avoiding confusion over multiple similar documents.

Documentation Practices

  • Members are encouraged to personalize their plans with relevant text or graphics, enhancing communication through visual documentation.
  • Simple documentation practices like adding text labels help clarify each person's contributions within shared plans.

Naming Conventions Importance

  • Proper naming conventions for plans allow easy identification among team members while preventing conflicts when synchronizing files across different users.

Collaboration and Synchronization in Revit

Initial Setup and Collaboration

  • The speaker discusses the importance of collaboration in a project, emphasizing the need for team members to synchronize their plans effectively.
  • Acknowledgment of potential issues if a team member is absent; synchronization can be forced under certain conditions.
  • It’s crucial that all participants have the same plan number; if one is occupied, it will be necessary to change it without losing any data.

Managing Plan Numbers

  • The process of assigning new numbers to plans is explained, highlighting how sequential numbering works when multiple users are involved.
  • Clarification on how plan numbers are assigned based on availability, ensuring no conflicts arise during collaboration.

Publication Configuration

  • Transitioning into publication settings; the speaker reassures that minor delays in synchronization are manageable.
  • Emphasis on keeping software updated and being cautious about frequent synchronization to avoid data loss.

Saving and Synchronizing Work

  • Importance of saving work locally before synchronizing with others is stressed; this ensures personal progress isn't lost due to connectivity issues.
  • The speaker explains how saving creates a backup on the local machine, which can be synchronized later.

Troubleshooting Connectivity Issues

  • Recommendations for handling slow internet connections during collaborative work; suggests adjusting update frequency settings in Revit.
  • Discussion about potential performance issues caused by poor internet connectivity while working collaboratively in Revit.

Final Steps in Collaboration Process

  • The speaker prepares for a final step in the collaboration process but indicates that only one person will execute it. Encouragement for team members to volunteer for tasks.

Collaboration and Configuration Steps

Group Coordination for Task Execution

  • The speaker emphasizes the need for one person from each group to handle specific tasks, encouraging collaboration without conflict.
  • Wilmer is designated to perform a particular step, highlighting the importance of synchronization among all participants during this process.
  • A suggestion is made to close and reopen a file if issues arise, indicating troubleshooting steps in collaborative work.

Understanding Publication Configuration

  • The discussion revolves around using a publication configuration tool that has been previously utilized by the groups.
  • Participants are instructed on how to create new sets for printing purposes, emphasizing the importance of understanding these configurations for future classes.

Creating New Sets and Managing Views

  • The speaker explains how to create a new set titled "entrega ARC" with specific formatting details (date included).
  • Instructions are provided on selecting architectural views and plans within the model, stressing the necessity of activating certain options while deactivating others.

Efficient Printing and Visibility Management

  • The goal is to streamline printing processes by preparing sets that include only necessary plans, thus saving time during presentations.
  • It’s noted that selected views will be visible in Autodesk Construction Cloud through web navigation after proper configuration.

Finalizing Changes and Synchronization

  • Participants are reminded about the importance of naming conventions when saving their work and ensuring visibility settings are correctly applied.
  • Emphasis is placed on experimenting with filters to view different combinations of plans before finalizing selections for printing.

Conclusion of Session Tasks

  • After completing their tasks, participants must synchronize files again to ensure all changes are updated across platforms.
  • The session concludes with instructions on publishing recent changes so that updates reflect accurately in Autodesk Construction Cloud.

Overview of Publishing Process in Project Management

Steps to Publish and Update Projects

  • The visible plans are those selected by Wilmer for publication, indicating a collaborative approach where multiple users can continue working simultaneously.
  • Discussion on the complexity of password management and calculations required for project access, highlighting the technical challenges faced during the publishing process.
  • Emphasis on real-time updates within the browser, suggesting that refreshing (F5) is necessary to see changes reflected immediately.
  • Instructor invites questions or clarifications regarding the current progress, stressing the importance of verifying all groups' statuses in future classes.
  • Acknowledgment of ongoing work processes and the need for continuous updates as part of effective project management.

Troubleshooting Connection Issues

  • A new publication appears available; however, connection issues with cloud services are noted, affecting visibility and updates.
  • Importance of checking recent changes made to ensure proper versioning; communication loss can hinder progress tracking.
  • Confirmation that updates are being processed correctly; anticipation for further developments in upcoming classes is expressed.

Future Class Expectations

  • Plans to continue discussions on design collaboration modules in future sessions, focusing on shared folders and their functionalities.
  • Reminder that installations must be updated accordingly; instructor hopes students have gained valuable insights from today's session.