Autodesk has announced its first-ever Autodesk PLM 360 User Conference, Accelerate 2014, to be held September 16-17 in Boston. This free event looks to be a great place not only to network with others in the Autodesk PLM 360 community and meet the Autodesk PLM 360 product and support teams, but also to hear from industry leaders and analysts about trends in product innovation and manufacturing.
Breakout sessions over the two-day conference are scheduled to include presentations by four customers who have utilized Razorleaf services for configuration, training, or integration for their PLM 360 platform. Autodesk PLM 360 is the company’s flagship PLM tool based on cloud computing. To learn more about PLM 360 and the services Razorleaf can provide, explore our PLM 360 page.
As an incentive, Autodesk is also providing attendees with a discount on their Autodesk University registration. For more information or to explore how your company might benefit from our PLM experts, contact us or look for our team at Accelerate 2014! And don’t forget to check out the conversation on Twitter using #AcceleratePLM14 as the event hashtag.
In July 2014, Dassault Systemes held an event specifically for ENOVIA users in Waltham, MA near the company’s North American headquarters. For the past several years, ENOVIA events have been connected with, or adjacent to, larger Dassault events such as the 3DEXPERIENCE Forum. Interestingly, this ENOVIA Community Conference addressed more than just the latest and greatest from Dassault’s ENOVIA product line; there was a significant amount of content around ENOVIA SmarTeam.
Back in 2013, SolidWorks released an add-in for Enterprise PDM which included most of the features of Razorleaf’s Office2PDM tool. This add-in is compatible with EPDM 2013 and EPDM 2014, so many Office2PDM users will no longer have significant need for a separate product to provide Office integration functions. As a result, Razorleaf has discontinued the Office2PDM product.
From time to time we encounter errors that leave even the most experienced of us puzzled. Such was the case with a problem we encountered with the ENOVIA SmarTeam Data Model Designer. If you’ve seen the message, “SmarTeam Internal Error” in the SmarTeam DMD, we have a possible resolution for you (this message can actually indicate many different problems, so we might or might not have the resolution to your specific problem).
Running the ENOVIA SmarTeam Data Model Designer is an important step in most upgrades, even when not explicitly required to update the SmarTeam schema. A lot of things happen in the DMD (Data Model Designer), even when there are no user-initiated schema changes. So a failure can be tricky to troubleshoot. Luckily, detailed troubleshooting guided our path to the solution in this case. Below are the initial symptoms encountered by members of our team, where the failure became evident, as well as the final resolution to the problem.
During the final stages of the DMD during an upgrade to ENOVIA SmarTeam V5-6R2014, after the DB registration settings dialog, the DMD attempted to set the new SMARTEAM_VERSION information as well as update the unique DB_VERSION string. At this stage, we received a message indicating that the DMD had failed, specifically “SmarTeam Internal Error”. This was followed by a second error dialog, “Modification of the destination database failed. Please revert to the database backup.” Since the errors were not specific enough to indicate the exact problem, we reviewed the DMD logs, which are located (for a Windows 2008 R2 server) in C:Users<logged in user>AppDataLocalSmarTeamCommonLOG. The SmartDataModelDesigner.log file unsurprisingly contains information about the DMD. Scrolling to the end of this file, we found that the DMD failed while updating the TDM_DB_VERSION table. “Failed to upgrade table TDM_DB_VERSION” was the specific error message.
Logically, we inspected the TDM_DB_VERSION table, only to find that ENOVIA SmarTeam had actually updated the table appropriately. We continued troubleshooting, looking at everything from SmarTeam destination version to source SmarTeam version to specific service packs of SmarTeam. In the end, the SmarTeam version and service pack were not related to the problem – it turned out that a detail related to the server’s configuration was the culprit.
An entry in Dassault System’s Knowledgebase (QA00000020164) helped identify the root cause of the problem (note that Dassault’s Knowledgebase entry is listed as applicable to SmarTeam V5R21):
Question: What to do if Data Model Designer fails with “Smarteam internal error” and “Failed to upgrade table TDM_DB_VERSION”?
Answer: This issue can occur if the Smarteam Service account user is not in the Administration group, so please check your login and service user.
In our case, the SmarTeam service account had accidentally been left out of the Windows Administrators group. We had overlooked this in our initial troubleshooting because we assumed that all SmarTeam needed was a connection to the underlying database. Although we don’t know the exact cause of our failure, it seems that this final step of the SmarTeam DMD must need some administrative access to Windows. We believe it could be related to writing to SmarTeam’s configuration settings, although we don’t have any specific evidence of this. Given the nature of the problem however, we expect that this issue could be applicable as far back as SmarTeam V5R16.
Hopefully that gives you some good direction if you’ve run into these issues before, and perhaps some insights into why it happens. As always, we’re happy to provide any direction and support that we can, please reach out to us if you need some help.
Ask people in the DriveWorks community about what was introduced in DriveWorks 11 and Triggered Actions will come up frequently. What may not come up is what DriveWorks Triggered Actions really are, how Triggered Actions are used, and why they’re worth digging into. Well it is time to clear this up once and for all.
Most major PLM vendors have a 2D and 3D visualization strategy based on their own proprietary file format. However, Aras has introduced a standards-based visualization strategy based on PDF, making PLM content more open, accessible, and widely consumable. Aras’ approach has impacts beyond PLM users and could open up 3D usage to entirely new categories of enterprise users.
Generations of children have stood in wonder on their first trip to a bowling alley, mesmerized by the smooth motion of the automatic pinsetters and the sight of brightly colored balls spinning up the ball return. The technology that makes a bowling alley operate isn’t magic – it just seems that way.
Behind the scenes AMF Bowling, a division of QubicaAMF , engineers a complex and carefully timed dance of moving parts to be both rugged and precise. AMF designs and fabricates most of the parts it uses and assembles everything from the ball returns to the laminates for the flooring. The pinspotter, for example, includes more than 3,800 different parts, all of which must be engineered to work smoothly without clashing.
Managing such complexity isn’t easy, as Brian Williamson, CAD-PDM Administrator and design engineer with QubicaAMF Worldwide, will be the first to admit. “When I got here four years ago, I think I spent more time trying to locate the designs for the parts in our machines than I did designing new ones,” he says. “CAD files were scattered all over the network and on local drives with very little chance of being found again so they could be reused.”