Mapping Business Process (Workflow)

Workflow, the mapping of processes relating to the flow of information through a business is another core function of PLM. The addition of workflow in PLM adds value beyond relationships. Businesses have formal and informal procedures that they execute manually which can become the maps for the design of workflows. For example, new part design gets initiated in engineering and goes through to production release. In establishing a workflow, we describe the manual process in its full detail in the form of a flow chart, a graphical representation of the definition, analysis, and solution to a task(s). A PLM system will come equipped with a comprehensive tool to graphically build and apply logic to the workflow processes that are required to accomplish business tasks. Because a business may have many workflows, which can vary in complexity, workflow planning is a critical process requiring careful analysis.

Creating Rules

PLM is rules driven. What this means is that every object within the PLM database is controlled by access rules. Determining who has access to what data is an integral part of implementing a PLM system. PLM systems typically assign people (users?) into the categories of User, Group, and Role. For example, Joe User is in the "Group" called Sourcing, and has the "Role" of Buyer. The complexity of an organization and its business processes can determine the quantity of rules the PLM system must provide. People in a PLM system will also be defined as Authors and Consumers, those who can create and edit information, as opposed to those who may only view information. Similar to people access, work flows also are controlled by rules. Work flow rules specify actions required in order to move an object(s) through its specified process. This can be as simple as determining who needs to be notified for a review task, and as complex as executing a change of state (such as change pending to be released) on objects and moving them to new locations.

Shared Access

So far we have classified objects and made them searchable. We have built relationships so that we can assign them to objects and tie them together in arrangements that are correct for our business. We have built work flows to map out how information flows through our business, and finally we have created a dynamic rules system to be certain that we build, revise, and view our business objects in a controlled manner, thereby maintaining the integrity of our data. Together these features combine to form an environment that allows many users to interact with business information simultaneously in a controlled manner.

Conclusion

The concepts of PLM are not difficult to grasp, but careful planning is the most significant consideration required for a successful PLM implementation. The concepts of PLM have been generalized, as there are many areas in a PLM deployment that can be configured according to varieties of business, types of information, and exact processes needed for each. The goal of this article has been to convey basic concepts of PLM, to give a clearer understanding of its potential benefits in business, and to provide a sense of the effort needed to successfully implement even the most rudimentary aspects of PLM.

About the Author

Steven Rashkow is a process consultant for a major provider of PLM software tools and services. Steve has over twenty years of experience in engineering design, software support and consultation. He enjoys writing about technical topics for non-technical readers.

Source: http://ezinearticles.com/