Does anyone know of a document showing the overall process to capture a business process in Windchill? I think I am picking up all the separate pieces, but am not entirely sure how they fit together in the puzzle yet....
Anyone have a good example they can share?
If not, I was thinking of a somewhat generic process like requesting a quote:
The Windchill Pieces I know about:
What am I missing?
You've got the basics pretty much covered as far as the Windchill items needed to actually get a process in place, but there are a few key components to think about. Here are a few:
I have worked on many projects involving incorporating business processes within Windchill and have built several strong solutions, fitting the pieces of the puzzle together in the best way. Feel free to reach out for additional advice, or if you'd like you can send me an e-mail and we could discuss bringing my company's services to your assistance.
Lots of ways to approach this - and this is the "art" of Windchill configurations and part of what makes it rewarding and fun. I do a lot of this on the side.
For the need identified above, you might consider using for example (just a few possibilities):
- Not using a different type but using a different LC / WF in a specific Library meant only for quote documents.
- Use a Project instead and use Project Document Route (could use OTB or configure a new Routing LC and associated WF. This has the major advantage of being able to evolve to where you no longer email any attachments, but instead add files to the Project as WTDocuments (possibly a sub type), the vendor picks them up directly, then deposits their quote in the same Project. All involved can get notified thru Routing WF and/or subscriptions. Can isolate vendors by different Projects or even by folders within a project.
- Can use a Windchill Package for this, collecting all needed info. Can make a separate Delivery for each vendor, and Revise and repeat as needed. Packages also have the opportunity to provide an offline-viewer of published content. Can choose to include only nuetral files, etc.
Consider that what you start can be simple but should be able to evolve. In general though, yes, the fundamental pieces are:
- Type / sub type (main reasons for a different type: attributes, permissions, LC/WF)
- OIR for the type, that specifies LC
- Possibly start WF from the LC for the object directly; alternately, start the WF from an intermediate object (e.g.. a Package)
- Solution may include templates
- Solution may include custom Searches made available to all users
- Solution may include custom query builder reports
Okay, maybe I don't as much as I thought...
For example, how do you initiate a workflow? In my example above, I was envisioning choosing a WTPart, and kicking off the RFQ workflow. But how?
You tie your LC State to a workflow and then when that state is selected the workflow kicks off. This shows a workflow for Creation but you can have one kick off for the state when you do a revise on the object that is different.
Assuming you want to run a workflow for that particular part and NOT use a Promotion Request or Change Object, then what you do is the following:
The two key use cases I have seen for this are:
Your workflow would most likely drive life cycle state changes too, which may or may not drive different paths in your flow or even different templates altogether.
As Mike brought up too, there are packages and routing functionality that may make more sense to use to communicate with vendors outside of your WC system. There really are very many ways to accomplish this.
AHHHHHHH! This is very frustrating and confusing. How does anyone learn this stuff?
I was told that you use basic lifecycle types for WTDocuments and CAD Documents etc.., and advanced lifecycles for the workflows that make changes to those objects. Like a promotion from In Work to Released. The object isn't using the advanced lifecycle, the promotion is.
Is this correct? If so, how do I apply that principle to my example?
i only learned this stuff from playing with it on my laptop for hundreds and hundreds of hours at home. The courses help with the mechanics but not so much how to "design" with the elements of the system like LC, WF, etc. (which is why consultants are needed in general)
Mike, I can appreciate that, and I will get there eventually. I don't have a budget for this and my boss is wanting results. Oh well...
That's what consulting is for .
I'd be happy to give you an assessment for free on how I would see your RFQ processes (and other processes, if applicable) would fit into your Windchill ecosystem. If you are interested, send me an e-mail and we can discuss further.