A blog by Oleg Shilovitsky
Information & Comments about Engineering and Manufacturing Software

How PLM can beat Excel? Or Blue Ocean’s ideas on how to improve usability…

How PLM can beat Excel? Or Blue Ocean’s ideas on how to improve usability…
olegshilovitsky
olegshilovitsky
2 March, 2009 | 2 min for reading

It looks like PDM is constantly running after Microsoft Excel. Lately PLM has also joined the chase.… While looking at the history of Excel applications, I’ve noticed a number of features in PDM/PLM systems that have been repeated systematically after similar features were introduced in MS Excel. In release after release, you can see sort, filter, groups, nested trees, etc.

 

Actually, PLM vendors are pretty aware about such competition. You can see multiple blogs and white papers comparing Excel capabilities and explaining why particular work can be done better in PLM compared to Excel. On the other hand, Excel provides people with a very flexible and open environment in which people can feel very secure about the way they manipulate data. In my opinion, this is a key reason for the continuing popularity of Excel. The PLM environment delivers specific functionality (i.e. for Bill of Material management) but put constraints on data manipulation. Therefore, in the end, it loses potentially attractive features.

Each new release of PLM software creates new features that simulate Excel capabilities on top of data models and constraints that Product Data Management established. So, how do you break this cyclic development and make customers happier?

In my view, the adoption of MS Excel services is a viable option to steer away from this feature competition. Excel services is one way to improve the PLM/Excel relationship, improve user adoption and get more functionality for the PLM environment.



PLM systems need to map the data models and PLM services to an Excel service model. It will allow you to render data and use more functionality inside of Excel So, useful data manipulation such as sorting, filtering and others will be easy available for the product development environment. In addition Excel services will not require data to be copied/imported/exported. Actually, Excel service-based implementation will be more SOA compliant and improve data consistency inside the organization.

I’d like to know if you have any experience with Excel services in your organization or have tried to implement it as part of your software.

Recent Posts

Also on BeyondPLM

4 6
30 April, 2014

One of my favorite keynotes last week at COFES 2014 took me to the definition of time paradox and how different...

20 June, 2025

More than a decade ago, I wrote a blog titled “How Many Buttons Do You Need in a PLM UI?”...

21 January, 2021

Earlier this week, I attended a PLM Spotlight session organized by PI DX. If you missed my earlier blog, please...

28 November, 2020

I want to come back to my conversations about the construction industry. If you’re long time readers of my blog...

24 February, 2017

It has been almost 5 years since Autodesk turned the switch “PLM cloud” on. Tech-clarity blog – Autodesk’s announced PLM...

3 November, 2009

Collaboration is very important for product development including different phases – design, engineering, manufacturing etc. “Collaborative factor” is playing a...

25 August, 2010

I’m continuing to explore various aspects of relations between PLM and social systems and tools in my blog. The social...

27 March, 2014

Yesterday’s post about how engineers can collaborate in the office, made me think about another aspect of collaboration – taking notes. You...

5 July, 2016

New technologies can redefine existing usage patterns. One of the biggest pains when you run you application on the desktop...

Blogroll

To the top