The Top 11 Mistakes to Avoid During Engineering Document Management Implementations and Upgrades, Part 1

Rolling out an enterprise-level document management solution across your organization can be a daunting task. While there’s no be-all, end-all method to implementation, setting up enterprise software does require several layers of planning and cross-communication. In fact, the success of the solution often relies as much on the implementation process as it does on the technology itself.

To better understand the do’s and don’ts of implementing your engineering document management system, we asked our Applications Consultants to compile a list of the top 11 mistakes they see companies make during Adept implementations—as well as suggestions on how to prevent these errors.

This installment covers the first 5 of the eleven mistakes to avoid. Stay tuned for Part 2, where we’ll cover the final 6 tips for a successful implementation.

1. Assigning too many administrators

One way that organizations stumble early out of the gate is in determining user rights. All too often, our Applications Consultants see companies grant all users Administrator-level access, or give individuals or departments admin rights when they really need low level access.

Limiting the number of Administrators helps to establish a clear line of control and eliminates conflicting approvals. After all, the last thing you need is for someone’s work to be undone by another user. We recommend that you start small and only elevate rights on an as-needed basis.

It’s best to assign one primary administrator and to assign lower level permissions, such as Library Administrator or Workflow Administrator, to designated users.

3. Cutting back on implementation onsite training days to “save money”

It’s not enough to roll out software and expect all the end-users to automatically adapt to new software. One of the recurring problems our Applications Consultants see onsite are customers not taking full advantage of their implementation training days.

The Synergis Technical Applications Consultants have over 40 years of experience installing and implementing Adept across the globe. The training and implementation time spent with them is of extremely high value and will ensure that your system is setup successfully to your specific needs and requirements. Often, companies who cut back on training need more assistance earlier in the adoption process. For example, being overly reliant on resources such as Helpdesk causes them to be less efficient than if they were well trained from the beginning. We recommend prioritizing training—either on-site or at our offices—to get the most out of Adept from the start.

4. Opting for manual file migration vs. custom file migration

Now for the nitty-gritty part of implementing engineering document management—migrating your data into Adept. While both manual and custom file migration can get the job done, consider the pros and cons of each before you make a decision.

Manual file migration provides an opportunity to clean files during the migration process; however, it requires users to be locked out of files for manual cleanup. Programmatic custom migration occurs off-site and therefore, doesn’t cause as much downtime. Make sure you carefully review your data with our data migration experts before you make a decision.

5. Becoming stuck in the “old perceptions”

Perhaps one of the most challenging aspects of implementing new software is letting go of “perceived requirements” and embracing the new challenge to think outside-the-box. For example, one perceived requirement can be an out-of-date workflow process that you’ve been using forever, but you know isn’t really efficient. It’s not always easy to change or tweak “the old ways of doing things” when adopting a new system.

In order to become the productivity powerhouse you’ve always hoped for, you’ll need to be flexible and open to new, innovative automation methods. We strongly recommend leveraging Adept to find better workflows and ways of working—even if this path can initially be uncomfortable or different. Ultimately, your team will work more efficiently.

 

Having a thorough implementation strategy in mind is crucial to making Adept a success. Avoid these common mistakes, and you’ll be golden. Subscribe to our blog and check back next week for Part 2 of our series.

Best Practices When Using EDM Vendor Services

The old adage “to fail to plan is to plan to fail” is certainly true when it comes to something as important as installing engineering document management (EDM) software. Research by Jim Brown of Tech-Clarity shows it is possible to achieve EDM implementation benefits rapidly by following a few key rules:

  • Use preconfigured best practices for security, part numbering, and other common information standards;
  • When possible, use standard workflows such as “release to manufacture” and “engineering change control;”
  • Limit initial customization; evaluate customization needs after full initial implementation and training.

As important as it is to minimize initial customization, no EDM system out of the box will offer an exact fit for every company. Many companies have workflows which evolved over years or decades; these processes do not need to be eliminated just because of automation. Other companies need customization to help unify far-flung engineering offices and long supply chains. Read More

Understanding the Business Value of Legacy Data, Part 2

In the first article in this series, I introduced the importance of clear thinking about legacy data when installing a product data management (PDM) system. I spent time recently talking to Todd Cummings, VP of Technology, about his nearly 20 years of experience helping companies of all sizes install and use Synergis Adept. One of the first things he told me was “If you haven’t worn that gift tie for several years, then it’s time to donate it to the Salvation Army.” Apply the idea to legacy data, Todd said, not as a hard-and-fast rule but “as more of a healthy challenge: don’t assume legacy data should automatically be put into the PDM/EDM system.”

It is all about the business value of the information. Todd advises clients to make business value the lens through which they review legacy data. If data created 10 years ago is still accessed by your field engineers and support team, it stays in.  When it comes to some projects—not all data is valuable. Every business is different. Read More

Understanding the Business Value of Legacy Data, Part 1

When a company invests in a new product data management (PDM) system like Synergis Adept, one of the first agenda items is (or should be) to decide what to do with legacy data (product/project information created in the past and not in active current use). When engineering information is first created it is always of high value. But over time, value diminishes. The rate of value decay varies by company. So, how important is it to make older engineering data a part of the new PDM?

Some companies want to sidestep the question. On one hand, some will think the best choice is to only use the new PDM system with current projects. On the other hand, some will think the way forward is to put everything into the PDM. Both of these choices are based on overly simplistic assumptions about the value of data. Read More

Bending Space and Time: A New Way to Think about Collaboration

In most engineering organizations there is an uneasy truce between teamwork and solo endeavor. The contributions of many people are necessary and the interactive processes move ideas from concept to reality. But generally speaking, each team member works best not in a meeting but when he or she enters into their personal creative zone. Time seems to stand still; performance is at its peak. Alone with their ideas and their design tools, engineers and other team members create information that becomes products or assets.

And then the ethereal bubble gets popped by collaboration. Others need the engineering data, and they usually need it in bits and pieces that require searching, compiling, copying, and sending. The processes of sharing take precious time away from the creative. In this day and age of global connectivity the sharing happens not in one particular space but across ever-increasing distances. It can feel as if space and time are collaboration hobgoblins conspiring to steal the creative bliss of engineering. Read More

Greene, Tweed’s Winning Recipe for Synergis Adept/SAP Integration

Greene, Tweed & Co. may be a major player on the global stage, but for most of its history, its engineering data had a decidedly local footprint, tucked away in different file shares around the world and typically painstakingly difficult to find and share.

That is until the manufacturer of high-performance elastomeric and thermoplastic materials embarked on a journey to deploy Synergis’ Adept Product Data Management (PDM) system to centralize its critical engineering assets, including SOLIDWORKS CAD files, and to automate approval workflows on a global scale. But Greene, Tweed wasn’t content to stop there. Its vision was to integrate the Adept PDM platform with its core ERP system to make engineering data accessible to a much broader audience.

Greene, Tweed, like many companies, sees value in syncing its core enterprise systems rather than fostering silos that prevent groups like engineering and manufacturing from readily exchanging data and working off the same page. That’s according to Steven Danasko, SAP Solution Specialist in Greene, Tweed’s IT Center of Excellence, Product Lifecycle Management, who was the key orchestrator of the project. Danasko says that beyond a desire for more centralized data repositories and integrated workflows, the Adept/SAP integration made sense from a financial standpoint because it opened up access to critical engineering data to existing ERP users without requiring investment in additional software licenses. Read More