Razorleaf Corporation » | Razorleaf Corporation

Change in Dassault Version Naming

Michael Craffey — Tue, 15 May 2012 22:27:21 +0000

Those accustomed to the familiar V5 version lexicon that has been in use by Dassault Systemès for roughly 15 years are soon to learn a new naming schema for all V5 products, starting with V5R22. There is method to Dassault's madness with the change in naming system, but the new versions are a mouthful. V5-6R2012 has officially replaced V5R22 as the name for the current release of Dassault's version 5 software. The purpose for the change is to indicate a level of compatibility with the V6 (version 6) platform that is being built in to the V5 platform. For instance, in CATIA V5-6R2012, the integration to ENOVIA V6 is built into CATIA without the need to install additional software. To be clear, the progression of recent (and planned future) Dassault releases of its V5 product line is:

V5R20 (February 2010)
V5R21 (July 2011)
V5-6R2012 (February 2012)
V5-6R2013 (expected Q1 2013)

To summarize, V is for "version", "5" describes the baseline platform, the "-6" indicates compatibility with the V6 platform, R delineates "release", and "2012" is the release year. You can read Dassault's announcement about V5-6R2012 here to learn about the enhanced V5 to V6 compatibility being offered with this release of the product. The change in version naming impacts all Dassault V5 products including:

CATIA
DELMIA
ENOVIA SmarTeam
ENOVIA VPLM
SIMULIA

For more information or to discuss your next upgrade, please contact us.

DriveWorks EPDM Number Plug-in

Jonathan Scott — Sun, 22 Apr 2012 15:37:27 +0000

Razorleaf’s integration between DriveWorks and SolidWorks EPDM Numbering makes assigning part numbers and other PDM sequences seamless.

DriveWorks is fantastic at generating new designs, drawings, and other design-related deliverables, and at an amazing pace. While this is great for quickly meeting customer demands, it requires some level of data management and many DriveWorks customers turn to SolidWorks Enteprise PDM for that need. If you're using DriveWorks with EPDM, this plug-in is essential to integrating the two systems. With this connector, DriveWorks seamlessly pulls new numbers from Enterprise PDM for generated parts, assemblies, drawings, and other deliverables. And the data stays connected so that EPDM recognizes the files when they are placed in the vault. With the DriveWorks EPDM Number Plug-in, users have the flexibility to assign numbers manually (via a macro button) or automatically, during state transitions. Because the plug-in was written as a DriveWorks Specification Task, it can be leverage numerous places throughout your DriveWorks implementation and you know it is compatible with the overall behavior of the system. And of course, the plug-in isn't limited to working on one file at a time - the tool can be used on multiple parts, assemblies, and drawings to assign an entirely new numbering scheme to your DriveWorks-generated designs.

$750

per customer

DriveWorks 7, 8, and 9

SolidWorks Enterprise PDM 2010, 2011, and 2012

Direct from Razorleaf, or through your SolidWorks reseller

DriveWorks Simulation Plug-in

Jonathan Scott — Sun, 22 Apr 2012 14:29:02 +0000

Razorleaf’s integration between DriveWorks and SolidWorks Simulation validates your automated custom designs with Finite Element Analysis.

DriveWorks has enabled you to take your standard offerings and expand them to offer the custom-designed solutions that your customers need and your competition can’t offer. But in some cases, your customized product isn’t ready to be delivered until the engineering behind it has been checked and verified. So whether you have legal requirements, reliability concerns, or just want that extra measure of certainty that your product will perform as expected, the DriveWorks Simulation Plug-in can speed up the process of performing finite element analysis on your automated designs. Razorleaf’s Simulation Plug-in for DriveWorks allows you to drive loads and restraints and perform simulation on your SolidWorks parts as they are generated automatically by DriveWorks. When paired with DriveWorks Autopilot, you can further automate the process and free up your workstation and your engineers, while providing that extra boost of confidence for both you and your client every time, with no extra effort. The plug-in provides support for:

Multiple Linear Static studies in a single part
Multiple analyses in a single specification
Driving of normal and uniform force magnitudes
Suppression states of individual forces and restraints

$2,500

per site

DriveWorks 7, 8, and 9

SolidWorks Simulation 2010, 2011, and 2012

Direct from Razorleaf, or through your SolidWorks reseller

ACE 2012 and Razorleaf

Jonathan Scott — Fri, 13 Apr 2012 12:30:28 +0000

Razorleaf will be attending the Aras Community Event 2012 at the beginning of May 2012 as part of our ongoing involvement in the PLM software community. The Read More...

New EPDM Reporting Training

Jonathan Scott — Thu, 12 Apr 2012 12:30:12 +0000

Razorleaf is proud to introduce a new training course focused on reporting for SolidWorks Enterprise PDM. The 3-day course, cleverly titled “Enterprise PDM Reporting,” is being Read More...

Razorleaf at COE 2012

Jonathan Scott — Wed, 11 Apr 2012 19:34:07 +0000

Even if you’re not able to attend COE 2012 Annual Conference this year, join us for live updates from the event by following us on Twitter. Razorleaf is also Read More...

SmarTeam V5R21 Compatibility

Michael Craffey — Wed, 29 Feb 2012 12:30:45 +0000

Dassault Systemès released ENOVIA SmarTeam V5R21 SP2 in November 2011 and V5R21 SP3 in February 2012. These latest releases are giving customers the ability to move forward with new system roll-outs, server upgrades, etc. on desired platforms. In general, SmarTeam V5R21 supports the latest Microsoft Windows server (Standard and Enterprise editions) and desktop operating systems in both 32 and 64 bit modes. The following server, desktop OS, and Office versions are supported:

Windows Server 2008 SP2 (32 and 64 bit), Windows Server 2008 R2 (64 bit only)
Windows XP Pro SP3 (32 bit), Windows XP Pro SP2 (64 bit)
Windows Vista Enterprise & Business SP1 (32 and 64 bit)
Windows 7 (64 bit)
Microsoft Office 2007 & 2010 (32 bit)

Database support has changed in V5R21. The following list of database platforms details the new compatibility options:

IBM DB2 9.5
Microsoft SQL Server 2008 SP2 (32 and 64 bit)
Microsoft SQL Server 2008 R2 (32 and 64 bit)
*Oracle 11g R2 (32 and 64 bit)

*NOTE: The SmarTeam client side will require Oracle 11g R2 (32 bit) if the database platform is Oracle. SmarTeam CAD compatibility continues to be timely. For SmarTeam V5R21 SP2 the following CAD integrations have been certified as compatible:

AutoCAD & Inventor 2011 (32 and 64 bit)
AutoCAD & Inventor 2012 (32 bit)
Solid Edge ST3 (32 and 64 bit, supported from GA release of V5R21)
SolidWorks 2011 & 2012 (32 and 64 bit)

With SmarTeam V5R21 SP3, certification for 64 bit AutoCAD 2012 & 64 bit Inventor 2012 are added to the list from SP2. Compatibility updates for CATIA V5 continue to have the same two back, one forward pattern. For example, SmarTeam V5R21 will be compatible with CATIA V5R19, V5R20, V5R21, and V5R22. Both the 32 and 64 bit versions of CATIA are supported. Note that Dassault is changing its naming convention for releases at V5R22 so V5R22 may actually have a different name when it is released (expected to be called V5-6R2012). Dassault continues to have regular major and service pack releases of SmarTeam and other V5 platform software. Continue to look and plan for updates to SmarTeam in 2012 and beyond. With all upgrades, please review the release documentation for the latest information regarding version support and compatibility listings. For more information or to discuss your next upgrade, please contact us.

DriveWorks 9 Released

Paul Gimbel — Tue, 28 Feb 2012 01:23:22 +0000

On February 16, 2012 at the DriveWorks World conference in San Diego, California, the latest version of the DriveWorks Design Automation and Sales Configuration software was released to the world. Along with significant performance increases, DriveWorks 9 introduced a couple of new goodies that most DriveWorks administrators and architects will appreciate. DriveWorks 9 introduces a completely new 3D Preview technology that allows DriveWorks Live web users to preview their designs in 3D without the use of resource-intensive plug-ins like eDrawings. DriveWorks Live 9, with this 3D Preview, supports a wide variety of browsers, platforms, and devices, including tablets. DriveWorks architects will notice the speed increases, some operations running more than 10% faster. New functionality adds the flexibility to embed child specifications, making DriveWorks projects more robust to support applications with unknown numbers of line items or components. All of DriveWorks 9's new features will be described at the upcoming DriveWorks What’s New sessions on the web (register through DriveWorks' customer portal on the www.driveworkspro.com site). You can also contact Razorleaf for any questions that you may have about how DriveWorks 9 will affect how you use DriveWorks.

ENOVIA SmarTeam SQLMonitor

Steve Stojanovski — Tue, 21 Feb 2012 14:41:54 +0000

ENOVIA SmarTeam Editor constantly interacts with the underlying database server to send and retrieve data. It can be very useful to monitor the SQL statements the application uses to interact with the database, especially in a troubleshooting scenario. This article describes the step-by-step process for enabling the SQLMonitor capabilities of ENOVIA SmarTeam Editor. The ENOVIA SmarTeam SQL monitoring function can be enabled/disabled by a SmarTeam user with SmarTeam administrative rights and with access to the SmarTeam System Configuration Editor. Note that the SmarTeam SQLMonitor works with any of the supported SmarTeam databases including SQL Server, Oracle, and DB2. To enable SQLMonitor, perform the following steps:

Login to SmarTeam System Configuration Editor as a user with admin rights in SmarTeam.
In the search box, enter “SQLMonitor” and click the Search button to run a search for the keys related to the SQLMonitor.
Click on the key SqlMonitor.Visible from the search results.
The default value for the key is set to "NO". Select the Add Value button to add a new value for the key.
For the Override Level dropdown value, there are three options. You can enable the SQLMonitor for ALL users, a specific site (SmarTeam Multi-Site related), or only for a specific machine (computer). It is recommended to only enable SQLMonitor for a specific machine and not all users. In our example, we will enable SQLMonitor at the machine level, for the machine with hostname “rlv00012”. The Value for the key must be "YES" in all uppercase characters as shown in the image.
Click the Save Changes button to save the key. The changes will now show in the set of key values for the SQLMonitor.Visible key.
Click the Logout link to exit from the SmarTeam System Configuration Editor.

The next time you start SmarTeam Editor on the designated machine (rlv00012 in this case), you will immediately see a window pop up on the top of the screen with the title “SmSqlMonitor – SmTdm32.dll”. The SQLMonitor window is a real-time log of all the SQL statements that this SmarTeam Editor machine is making to the database server. The Mark button in the SQLMonitor window allows you to enter your own text into the SQLMonitor window. You can use this to set a marker in the log to denote the start and end of certain operations that you perform in SmarTeam Editor. For instance, you may want to see all of the SQL statements that are used during the login process, or during a Check In operation, or some other SmarTeam function. The Clear button simply clears the window of the log. The Save to File button allows you to save the contents of the SQLMonitor window to a file. Be sure to enter the full path where you want the file saved; something like "c:\SQLLog.txt" is easy to enter, and easy to find. Once you save the file, it will not keep saving the SQLMonitor output to the file. You will need to save any new output to the file each time you want it captured.

To disable the SQLMonitor functionality, you simply need to login to the SmarTeam System Configuration Editor, search for the SQLMonitor.Visible key, and delete the specific entry that you added previously to enable it, or set the "YES" value to "NO" in case you want to perform future monitoring activities. The ENOVIA SmarTeam SQLMonitor functionality makes a great addition to your toolkit for troubleshooting (and even scripting) ENOVIA SmarTeam. Give it a try and leave us a comment if you have an interesting use for it.

Aras EPLM for SolidWorks EPDM

Jonathan Scott — Tue, 25 Oct 2011 13:00:41 +0000

Aras EPLM, a new commercial offering from Aras, is available now for managing SolidWorks, AutoCAD, Inventor, Solid Edge, and Pro/Engineer data in an enterprise PLM solution. The EPLM tool provides pre-configured PLM functionality on top of SolidWorks Enterprise PDM (EPDM) to give new and existing EPDM users an ability to scale up to PLM quickly while retaining best-in-class CAD data management. Interesting things to note about Aras EPLM for SolidWorks Enterprise PDM:

Web-based for globally distributed access across locations, and out to the extended enterprise (suppliers and vendors)
Enabled on the Microsoft technology stack just like Enterprise PDM
Item-based, process-oriented, and scalable with a variety of Aras Innovator domain-specific PLM solutions

Aras EPLM offers PLM functionality such as:

Engineering BOM Management
Enterprise Change Management
Integrated Project Management
Effectivity & Baselines
Item Classification
Alternate & Substitute Items
Item Lifecycle

You can read more about Aras EPLM on the Aras website, and learn more about deploying the solution by reaching out to us. Please contact us if you’re interested in Aras EPLM and would like to extend your SolidWorks Enterprise PDM capabilities – we’d be happy to help.