All Collections
loadmodeling.tool FAQ
Transitioning to a new Load Modeling Software
Transitioning to a new Load Modeling Software

Adopting a new load modeling tool, change best practices

Patrick Chopson avatar
Written by Patrick Chopson
Updated over a week ago

Change is difficult, but it can also be a deeply rewarding process.

In the Architecture, Engineering, and Construction industry there have been two major changes over the past several decades. Few of us who have practiced during this time would describe these as "smooth transitions." First, the change from hand drawing to computer aided design (CAD) was profoundly impactful on the profession. Following this change, the evolution of CAD to building information modeling (BIM) generated a lot of frustration, and with good reason. This has left many in the industry understandably hesitant to adopt yet another change.

Following is an overview of what a change in load modeling software might look like, along with recommendations for successful adoption. We will review what to do with projects completed in legacy software, training the team on the new platform, and what improvements new software will bring.

What to do with Projects in Legacy Software

Many of the legacy software available are built on proprietary simulation engines and file types. This makes it extremely difficult to translate models into modern tools, even if the new tool is open source. Here are some guidelines to help you maintain access to your legacy projects:

  1. Ask the legacy software vendor if they have a transition plan in place.

  2. Maintain at least one license for the legacy software.

  3. Archive all model files and store them in backed-up project folders.

  4. Export all available reports into PDF so your firm can access them without the source model.

Training Your Team and Preparing for Change

There is no single best means of training staff or on boarding new software. Each individual of a team will have their own style of learning, comfort with technology, and desire for change. Here are some guidelines to help onboard, and train your team on new software.

  1. Do not force change all at one. Have a roll out plan that transitions slowly

  2. Identify champions who are most interested in exploring new tools or who have been having the most challenges with legacy tools.

  3. Use the tool on specific projects, record success stories, and lessons learned.

  4. Share these successes and continue to roll out the new tool onto more projects.

  5. Provide formal training and self-paced training engineers can take as needed while considering initiatives that motivate participation.

  6. Maintain access to legacy projects for engineers and projects that have not made the switch, do not force the change.

Improvements with new Software

New software and technology should, at its core make our lives easier. When making a change identifying and tracking the improvements we expect is important. This provides a reason for the change and a way to validate that the change is successful. Here are some improvements to look for and how to track each one.

  1. Reduced geometry time

    1. Track time from modeling start to first results produced. Create a metric of analysis that captures the operational impact, including costs, associated with time savings.

  2. Reduced errors in the results

    1. Track number of comments each modeler receives when projects are reviewed. Survey current model reviews as a baseline and target a reduction to set goals for success.

  3. Reduced engineer fatigue

    1. Survey the team to understand their baseline experience. After adoption or initial review, survey the team again and look for improved moral, fewer overtime hours spent, or process improvements.

  4. Increased collaboration between team members

    1. Survey the time between questions "asked and answered." This is a significant challenge for many firms, especially when modeling and/or simulation takes days or weeks to produce and an opportunity for innovation.

    2. Record how the adopted software or technology facilitates team collaboration and reduces this time associated with your client interactions and internal processes.

Finally, new software should allow for more flexibility than legacy tools. Here are some items to prioritize in your analysis.

  1. Open Source based tools

    1. Software that is based on open source engines will be readable by other tools. This means your team will not be locked into a single platform again.

  2. Multiple means of generating geometry

    1. Buildings are unique and no single workflow will be perfect for every project. Software should provide varied and flexible means of creating geometry to meet the needs of different projects.

Want to learn more about loadmodeling.tool for your team?

Did this answer your question?