SolidWorks:HEARD! - Episode 436 - Kenesto Community

/
SolidWorks_Heard_Logo_2012_V2_Small.png

Kenesto Community:

This podcast covers the free Kenesto Community, a cloud service that brings business process workflow and social interactivity into one hosted community.  Kenesto came on the radar a couple years ago at SWW 2012 but was still under beta at the time.  Topics covered:

- What does Kenesto Community do?​

- What are the costs of the business plans and what do they offer?​

- The feature list and how it blends workflow with social.​

- Use cases and highlights

- Overall impressions

​I had heard about Kenesto in the early months before SolidWorks World 2012 in San Diego, CA and that Mike Payne, long time CAD pioneer, was taking the PLM and business process automation (BPA) to the cloud.  The early promises were to take the infrastructure load off of customers and centralize this automation in the cloud. 

I first saw the product at their booth in the SolidWorks World Partner Pavillion where I got a demo and a more concise description of their goals and product roadmap.  Since then the product fell off my radar since the launch was not quick and it appeared that the beta was going to take some time.  ​However, earlier this year there was a shift when Kenesto brought on Steve Bodnar from Autodesk to head up products and marketing.

This year (2013) they are now expanding upon their hosted workflow and integrating a social layer and "Freemium" model to get users familiar with the service.  Kenesto offers collaboration and discussion around tasks, documents, workflows, links, forms and a number of other aspects important to project/process management.​

Check out the SolidWorks:Heard! Blog and follow us on Google+, Twitter, Facebook and THE HEaRD!

SolidWorks:Heard! - Episode 397 - Workgroup to Enterprise

/
​

Workgroup to Enterprise:

This podcast discuses the challenges and preparation when considering the move from SolidWorks Workgroup PDM to Enterprise PDM.  Although this transition is common, not every transition is the same.  Topics covered:

- When to consider migrating

- How the major differences in the two PDM products factor in

- What is involved in migrating data

- How to prep the move to EPDM

- Types of migration to consider

- Post migration activities

The dynamics of design are changing.  Remote teams, larger data sets, complex change processes, ERP/MRP systems, etc and with that the task of tracking data during design grows in importance.  PDM (Project Data Management) tools have often been looked at as a final resting place (therefore the nickname VAULT).  But as teams work together and data is constantly changing, tracking of file versions and revision schemes during design has become more "In-Process" management.

In the SolidWorks family of products, Workgroup and Enterprise PDM are two products that are used and the question of when to move from WPDM to EPDM is considered when the design process outgrows or strains the workgroup mentality.  Although migration from WPDM to EPDM is a common activity, the process and result are vastly different depending on a number of factors.

Since I am performing a major migration this weekend, I thought it was worth discussing this process and what I see when I work with companies that take this journey.  Migration is not a perfect process but there are a number of things that one can do to ease the stress and allow for a smooth rollout.  ~Lou

Check out the SolidWorks:Heard! Blog and follow us on Google+, Twitter, Facebook and THE HEaRD!