Main (#1) - Questions - lifecycles (#90) - Message List
I am having a bit of trouble understanding the lifecycle - state - lifecyclestate
According to the requirements, there must be draft, official, optional and deprecated states. Why are there different states to lifecycles?
While I am not an expert PLM user, I have some experience. In the setup of my current company, we have only lifecycles - Draft, Design and In Production. Basically Draft is uncontrolled (changes can be made at any time), Design means that you have to up-rev anything with a change, and In Production requires an ECO to make any change.
My preference would be to have a system set up in OpenPLM that is very similar, but I'm really missing why Lifecycles have states and what the function of those states actually is. Also, I am not sure why we need to set up a lifecycle, a state and a lifecycle-state. Any help with understanding is greatly appreciated.
I should add that I have gone through the documentation and haven't been able to completely figure this out.
Thanks in advance, Matt
You say :
In the setup of my current company, we have only lifecycles - Draft, Design and In Production
To me, "draft", "Design" and "In Production" are states in openPLM. And states are linked into a lifecycle. Each object (part, document or ECO) have a proper lifecycle and this lifecycle has states and one of them is the current state.
OpenPLM has some pre-defined lifecycles :
- lifecycle1 : Draft, Official and Deprecated
- lifecycle2 : Draft, Proposed, Official, Deprecated
- lifecycle3 : Design in progress, Ready for tooling, Ready for pre-production, Ready for production, Deprecated
But you can design your own lifecycles with your own states. The rules you must respect, you must have :
- a state that is set for object creation (equivalent to draft state),
- a so-called "official" state (equivalent to your "In production" state
- and a state for old/deprecated/obsolete objects.
The ECO system you talk about is not implemented yet. We started an ECR (Engineering Change Request) but not an ECO (Engineering Change Order). Even if I've developed something similar for a customer, it's not in the shared source code.
I hope it answers to your topic.
Philippepjoulaud12/22/15 09:12:45 (3 years ago)
Thank you for your reply - I think I understand now.
Basically in the terms of OpenPLM, our current system has only one defined "lifecycle" of which the states are: Draft, Design, In Production (we also have Abandoned, which would correlate to Deprecated). OpenPLM has the ability to define additional lifecycles with associated states.
When you have developed an ECO system for a customer, is the use of an ECO to make changes in certain lifecycle states enforced (meaning that it is not possible to promote an item to "Official" or "Production" without an ECO)?
Thanks, Mattthemedulla12/22/15 21:00:27 (3 years ago)