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

Lifestream Concept for PLM Applications

Lifestream Concept for PLM Applications
olegshilovitsky
olegshilovitsky
13 March, 2009 | 2 min for reading

As you know, new ideas often come from things already forgotten… Therefore, I like looking at research projects and experimental products as they are good ways to find some fresh ideas. A few days ago, I was looking at the Lifestream application created by Gelernter 1994; Freeman 1997. 


lifestream

 

Another predecessor and association is Malone’s influential study – “How Do People Organize Their Desks?” (1983). I found some very interesting concepts that, in my opinion, can be valuable for Product Lifecycle Management. What particularly caught my attention was the association between lifecycle and Lifestream. Actually, in regards to lifecycles, I think that we are very disconnected from representation of time in PLM applications.

lifestream

 Lifestream is about time. Originally, the proposed approach was to throw away filenames, folders and static filling and replace it with stream of information arranged according to time. Actually after the implementation of Lifestream, some of its features were found in Apple iApps and other commercial products.

[youtube=http://www.youtube.com/watch?v=n055CqFnjyo]

While terms such as file/folders/desktop are brilliant, but Lifestream focused on the non-traditional aspects of information management, which is not typical for regular computer users. On the same point, I think PLM is different as a good concept of managing of product data that needs to be invented.

The Lifestream model is about to create, organize and present timelines. Whereas timelines may have different representations – collections, calendars or queries, this model would eliminate all other artificial models that people need to create in order to store product information. It’s interesting that this model would allow you to use a “time oriented” memory. An additional benefit of this approach is that the timescale lets you use the same model to manage tasks by leveraging future timelines. Appropriated information “tagged with future date/time” would appear in the scope of the system whereby the user would get this information as an alert.

lifestream-homepage

I think this is definitely an interesting concept that requires additional research and validation with users. I’d be glad to hear your comments and thoughts. 

Recent Posts

Also on BeyondPLM

4 6
2 February, 2010

I want to propose an unusual theme for our PLM discussion. Let’s talk about trends related to manufacturing and software...

10 September, 2022

Ask two engineers about something and you can easily end up with three (or sometimes more) opinions about how to...

1 May, 2015

Connectivity and information technologies are changing our lives. Think about your everyday experience – news, driving, communication, banking. It is...

28 April, 2024

In the world of engineering and product lifecycle management (PLM), Excel and other forms of spreadsheets have long been well...

9 June, 2024

The reality of every engineering team or manufacturing enterprise is multiple systems. For the last 20+ years, the question of...

9 April, 2010

I’d like to follow my yesterday post about PLM data modeling and talk about one of the issues that in...

29 June, 2017

Earlier today, I was honored to be a keynote speaker at CONTACT Software Open World 2017 user event in Fulda,...

29 October, 2019

I’m coming to Autodesk Forge DevCon – a pre-conference before Autodesk University. As in the last year, it will take...

29 April, 2011

BeyondPLM panel discussion on ACE 2011 View more presentations from Oleg Shilovitsky

Blogroll

To the top